Devices, Methods, and Graphical User Interfaces for Providing a Home Button Replacement

ABSTRACT

An electronic device with a display and an embedded fingerprint sensor displays a lock screen on the display. While displaying the lock screen, the electronic device detects a first touch input on the embedded fingerprint sensor. In response to detecting the first touch input on the embedded fingerprint sensor: the electronic device, in accordance with a determination that first timing criteria are met, displays content of a plurality of messages; and the electronic device, in accordance with a determination that second timing criteria, different from the first timing criteria are met, ceases to display the lock screen and displaying a home screen use interface for the electronic device with a plurality of application icons.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.17/203,667, filed Mar. 16, 2021, which is a continuation of U.S.application Ser. No. 16/521,433, filed Jul. 24, 2019, now U.S. Pat. No.10,996,766, which is a continuation of U.S. application Ser. No.15/814,051, filed Nov. 15, 2017, now U.S. Pat. No. 10,365,814, whichclaims priority to U.S. Provisional Application Ser. No. 62/506,837,filed May 16, 2017, which are incorporated by reference herein in theirentireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that provide a home button replacement.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Example touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterfaces and objects therein on a display. Example user interfaceobjects include digital images, video, text, icons, and control elementssuch as buttons and other graphics.

Some electronic devices, such as handheld devices, include a permanenthome button on the front face of the device that, when activated in apredetermined manner (e.g., when pressed for a single time), dismisses acurrently displayed user interface and displays a home screen of thedevice. However, a home button on the front face of the device reducesthe space available for the touch-sensitive surface (e.g., atouch-screen display) on the device, but removal of the home button fromthe front face of the device removes a convenient way for a user toaccess the home screen and other functions associated with the homebutton.

SUMMARY

Accordingly, there is a need for electronic devices with improvedmethods and interfaces for providing a home button replacement. Suchmethods and interfaces optionally complement or replace conventionalmethods for using a permanent home button on the front face of a device.Such methods and interfaces reduce the number, extent, and/or nature ofthe inputs from a user and produce a more efficient human-machineinterface. For battery-operated devices, such methods and interfacesconserve power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device is a personal electronic device(e.g., a wearable electronic device, such as a watch). In someembodiments, the device has a touchpad. In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen” or“touch-screen display”). In some embodiments, the device has a graphicaluser interface (GUI), one or more processors, memory and one or moremodules, programs or sets of instructions stored in the memory forperforming multiple functions. In some embodiments, the user interactswith the GUI primarily through stylus and/or finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, spreadsheet making, game playing, telephoning, videoconferencing, e-mailing, instant messaging, workout support, digitalphotographing, digital videoing, web browsing, digital music playing,note taking, and/or digital video playing. Executable instructions forperforming these functions are, optionally, included in a non-transitorycomputer readable storage medium or other computer program productconfigured for execution by one or more processors.

In accordance with some embodiments, a method is performed at a devicewith a touch-sensitive surface and a display. The method includes: whilethe device is in an unlocked state, detecting a sequence of one or moreactivations of a button of the device that includes at least a firstactivation of the button, wherein the first activation of the button isdetected while a respective application user interface other than a homescreen of the device is displayed on the display; and in response todetecting the sequence of one or more activations of the button of thedevice: in accordance with a determination that the first activation ofthe button was detected without a second activation of the button beingdetected before a respective threshold amount of time from detecting thefirst activation of the button had elapsed, replacing display of therespective application user interface with display of a home screen ofthe device while maintaining the device in the unlocked state; and inaccordance with a determination that the first activation of the buttonwas detected with a second activation of the button being detectedbefore the respective threshold amount of time from detecting the firstactivation of the button had elapsed, switching the device from theunlocked state, in which the respective application user interface isdisplayed, to a locked state.

In accordance with some embodiments, a method is performed at a devicewith a touch-sensitive surface and a display. The method includes:displaying a home screen on the display, wherein the home screenincludes a plurality of application launch icons that correspond to aplurality of applications that are installed on the device; whiledisplaying the home screen, detecting a first input by a first contacton a first application launch icon that meets application-launchcriteria; in response to detecting the first input on the firstapplication launch icon that meets the application-launch criteria,replacing the home screen with a first user interface of a firstapplication that corresponds to the first application launch icon; whiledisplaying the first user interface, detecting a second input by asecond contact that includes movement across the display in a firstdirection; and in response to detecting the second input: in accordancewith a determination that the second input meets dock-display criteria,wherein the dock-display criteria require that the second input includesmovement of the second contact with a magnitude of a movement parameterthat is above a first movement threshold in order for the dock-displaycriteria to be met, displaying a user interface object overlaid on aportion of the first user interface, wherein the user interface objectincludes a first subset of application launch icons from the pluralityof application launch icons; and in accordance with a determination thatthe second input meets home-display criteria, wherein the home-displaycriteria require that the second input includes movement of the secondcontact with a magnitude of the movement parameter that is above asecond movement threshold that is greater than the first movementthreshold, replacing display of the first user interface with display ofthe home screen.

In accordance with some embodiments, a method is performed at a devicewith a touch-sensitive surface and a display. The method includes:displaying a home screen on the display, wherein the home screenincludes a plurality of application launch icons that correspond to aplurality of applications that are installed on the device; whiledisplaying the home screen, detecting a first input by a first contacton a first application launch icon that meets application-launchcriteria; in response to detecting the first input on the firstapplication launch icon that meets the application-launch criteria,replacing the home screen with a first user interface of a firstapplication that corresponds to the first application launch icon; whiledisplaying the first user interface, detecting a sequence of one or moreinputs performed by a second contact; and in response to detecting thesequence of one or more inputs performed by the second contact: inaccordance with a determination that the sequence of one or more inputsincludes a second input by the second contact that meetshome-button-display criteria, wherein the home-button-display criteriarequire that the second input includes an initial movement of the secondcontact across the touch-sensitive surface in a first direction in orderfor the home-button-display criteria to be met, displaying a userinterface object overlaid on the first user interface, wherein the userinterface object includes a home button that is associated withdisplaying the home screen of the device; and in accordance with adetermination that the sequence of one or more inputs includes a thirdinput by the second contact that meets display-home criteria, whereinthe display-home criteria require that a characteristic intensity of thesecond contact increases above a first intensity threshold in order forthe display-home criteria to be met, replacing display of the first userinterface with display of the home screen.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensity of contacts with the touch-sensitive surface, one ormore processors, memory, and one or more programs; the one or moreprograms are stored in the memory and configured to be executed by theone or more processors and the one or more programs include instructionsfor performing or causing performance of the operations of any of themethods described herein. In accordance with some embodiments, acomputer readable storage medium has stored therein instructions whichwhen executed by an electronic device with a display, a touch-sensitivesurface, and optionally one or more sensors to detect intensity ofcontacts with the touch-sensitive surface, cause the device to performor cause performance of the operations of any of the methods describedherein. In accordance with some embodiments, a graphical user interfaceon an electronic device with a display, a touch-sensitive surface,optionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface, a memory, and one or more processors to executeone or more programs stored in the memory includes one or more of theelements displayed in any of the methods described herein, which areupdated in response to inputs, as described in any of the methodsdescribed herein. In accordance with some embodiments, an electronicdevice includes: a display, a touch-sensitive surface, and optionallyone or more sensors to detect intensity of contacts with thetouch-sensitive surface; and means for performing or causing performanceof the operations of any of the methods described herein. In accordancewith some embodiments, an information processing apparatus, for use inan electronic device with a display and a touch-sensitive surface, andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface, includes means for performing or causingperformance of the operations of any of the methods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface are provided with improved methods andinterfaces for providing a home button replacement, thereby increasingthe effectiveness, efficiency, and user satisfaction with such devices.Such methods and interfaces may complement or replace conventionalmethods for using a permanent home button on the front face of a device.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments.

FIG. 1C is a block diagram illustrating a tactile output module inaccordance with some embodiments.

FIG. 2A illustrates a portable multifunction device having a touchscreen in accordance with some embodiments.

FIGS. 2B-2C show exploded views of a force-sensitive input device inaccordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an example user interface for a menu of applicationson a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display inaccordance with some embodiments.

FIGS. 4C-4E illustrate examples of dynamic intensity thresholds inaccordance with some embodiments.

FIGS. 5A1-5A7 illustrate example user interfaces for displayingdifferent user interfaces and/or locking the device in response todifferent activations of a button in accordance with some embodiments.

FIGS. 5B1-5B22 illustrate example user interfaces for displaying a dockand/or the home screen of a device in response to a multi-stage gesturein accordance with some embodiments.

FIGS. 5C1-5C50 illustrate example user interfaces for displaying anon-demand virtual home button and activating the virtual home button todisplay the home screen in response to a continuous gesture inaccordance with some embodiments.

FIGS. 6A-6E are flow diagrams illustrating a method of displaying thehome screen without locking the device, or locking the device, dependingon different activations of a button in accordance with someembodiments.

FIGS. 7A-7C are flow diagrams illustrating a method of displaying a dockand/or the home screen of a device in response to a multi-stage gesturein accordance with some embodiments.

FIGS. 8A-8D are flow diagrams illustrating a method of displaying anon-demand virtual home button and activating the virtual home button todisplay the home screen in response to a continuous gesture inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Some electronic devices, such as handheld devices, include a permanenthome button on the front face of the device that, when activated in apredetermined manner (e.g., when pressed for a single time), dismisses acurrently displayed user interface and displays a home screen of thedevice. However, a home button on the front face of the device reducesthe space available for the touch-sensitive surface (e.g., atouch-screen display) on the device, but removal of the home button fromthe front face of the device removes a convenient way for a user toaccess the home screen and other functions associated with the homebutton. The embodiments below address this problem by providingalternative ways to access and activate a home button without having apermanent home button on the front face of the device.

Below, FIGS. 1A-1B, 2, and 3 provide a description of example devices.FIGS. 4A-4B, 5A1-5A7, 5B1-5B22, and 5C1-5C50 illustrate example userinterfaces for providing a home button replacement. FIGS. 6A-6Eillustrate a flow diagram of a method of displaying the home screenwithout locking the device, or locking the device, depending ondifferent activations of a button. FIGS. 7A-7C illustrate a flow diagramof a method of displaying a dock and/or the home screen of a device inresponse to a multi-stage gesture. FIGS. 8A-8D illustrate a flow diagramof a method of displaying an on-demand virtual home button andactivating the virtual home button to display the home screen inresponse to a continuous gesture. The user interfaces in FIGS. 5A1-5A7,5B1-5B22, and 5C1-5C50 are used to illustrate the processes in FIGS.6A-6E, 7A-7C, and 8A-8D.

Example Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Example embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch-screen displays and/or touchpads),are, optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a note taking application, a drawing application,a presentation application, a word processing application, a websitecreation application, a disk authoring application, a spreadsheetapplication, a gaming application, a telephone application, a videoconferencing application, an e-mail application, an instant messagingapplication, a workout support application, a photo managementapplication, a digital camera application, a digital video cameraapplication, a web browsing application, a digital music playerapplication, and/or a digital video player application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output” isphysical displacement of a device relative to a previous position of thedevice, physical displacement of a component (e.g., a touch-sensitivesurface) of a device relative to another component (e.g., housing) ofthe device, or displacement of the component relative to a center ofmass of the device that will be detected by a user with the user's senseof touch. For example, in situations where the device or the componentof the device is in contact with a surface of a user that is sensitiveto touch (e.g., a finger, palm, or other part of a user's hand), thetactile output generated by the physical displacement will beinterpreted by the user as a tactile sensation corresponding to aperceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2 ) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2 ).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds to userinterface objects. As used herein, the term “affordance” is auser-interactive graphical user interface object (e.g., a graphical userinterface object that is configured to respond to inputs directed towardthe graphical user interface object). Examples of user-interactivegraphical user interface objects include, without limitation, a button,slider, icon, selectable menu item, switch, hyperlink, or other userinterface control.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based on hapticand/or tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In an example embodiment, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In an example embodiment, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, California.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 167 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 167 receive tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch-sensitive display system 112, which islocated on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled with peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled with an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch-screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3 . Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, California. In some embodiments, theexternal port is a Lightning connector that is the same as, or similarto and/or compatible with the Lightning connector used in some iPhone®,iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes varioussoftware components for performing various operations related todetection of contact (e.g., by a finger or by a stylus), such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts or stylus contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

In some embodiments, detecting a finger tap gesture depends on thelength of time between detecting the finger-down event and the finger-upevent, but is independent of the intensity of the finger contact betweendetecting the finger-down event and the finger-up event. In someembodiments, a tap gesture is detected in accordance with adetermination that the length of time between the finger-down event andthe finger-up event is less than a predetermined value (e.g., less than0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensityof the finger contact during the tap meets a given intensity threshold(greater than a nominal contact-detection intensity threshold), such asa light press or deep press intensity threshold. Thus, a finger tapgesture can satisfy particular input criteria that do not require thatthe characteristic intensity of a contact satisfy a given intensitythreshold in order for the particular input criteria to be met. Forclarity, the finger contact in a tap gesture typically needs to satisfya nominal contact-detection intensity threshold, below which the contactis not detected, in order for the finger-down event to be detected. Asimilar analysis applies to detecting a tap gesture by a stylus or othercontact. In cases where the device is capable of detecting a finger orstylus contact hovering over a touch sensitive surface, the nominalcontact-detection intensity threshold optionally does not correspond tophysical contact between the finger or stylus and the touch sensitivesurface.

The same concepts apply in an analogous manner to other types ofgestures. For example, a swipe gesture, a pinch gesture, a depinchgesture, and/or a long press gesture are optionally detected based onthe satisfaction of criteria that are either independent of intensitiesof contacts included in the gesture, or do not require that contact(s)that perform the gesture reach intensity thresholds in order to berecognized. For example, a swipe gesture is detected based on an amountof movement of one or more contacts; a pinch gesture is detected basedon movement of two or more contacts towards each other; a depinchgesture is detected based on movement of two or more contacts away fromeach other; and a long press gesture is detected based on a duration ofthe contact on the touch-sensitive surface with less than a thresholdamount of movement. As such, the statement that particular gesturerecognition criteria do not require that the intensity of the contact(s)meet a respective intensity threshold in order for the particulargesture recognition criteria to be met means that the particular gesturerecognition criteria are capable of being satisfied if the contact(s) inthe gesture do not reach the respective intensity threshold, and arealso capable of being satisfied in circumstances where one or more ofthe contacts in the gesture do reach or exceed the respective intensitythreshold. In some embodiments, a tap gesture is detected based on adetermination that the finger-down and finger-up event are detectedwithin a predefined time period, without regard to whether the contactis above or below the respective intensity threshold during thepredefined time period, and a swipe gesture is detected based on adetermination that the contact movement is greater than a predefinedmagnitude, even if the contact is above the respective intensitythreshold at the end of the contact movement. Even in implementationswhere detection of a gesture is influenced by the intensity of contactsperforming the gesture (e.g., the device detects a long press morequickly when the intensity of the contact is above an intensitythreshold or delays detection of a tap input when the intensity of thecontact is higher), the detection of those gestures does not requirethat the contacts reach a particular intensity threshold so long as thecriteria for recognizing the gesture can be met in circumstances wherethe contact does not reach the particular intensity threshold (e.g.,even if the amount of time that it takes to recognize the gesturechanges).

Contact intensity thresholds, duration thresholds, and movementthresholds are, in some circumstances, combined in a variety ofdifferent combinations in order to create heuristics for distinguishingtwo or more different gestures directed to the same input element orregion so that multiple different interactions with the same inputelement are enabled to provide a richer set of user interactions andresponses. The statement that a particular set of gesture recognitioncriteria do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the particular gesturerecognition criteria to be met does not preclude the concurrentevaluation of other intensity-dependent gesture recognition criteria toidentify other gestures that do have a criteria that is met when agesture includes a contact with an intensity above the respectiveintensity threshold. For example, in some circumstances, first gesturerecognition criteria for a first gesture—which do not require that theintensity of the contact(s) meet a respective intensity threshold inorder for the first gesture recognition criteria to be met—are incompetition with second gesture recognition criteria for a secondgesture—which are dependent on the contact(s) reaching the respectiveintensity threshold. In such competitions, the gesture is, optionally,not recognized as meeting the first gesture recognition criteria for thefirst gesture if the second gesture recognition criteria for the secondgesture are met first. For example, if a contact reaches the respectiveintensity threshold before the contact moves by a predefined amount ofmovement, a deep press gesture is detected rather than a swipe gesture.Conversely, if the contact moves by the predefined amount of movementbefore the contact reaches the respective intensity threshold, a swipegesture is detected rather than a deep press gesture. Even in suchcircumstances, the first gesture recognition criteria for the firstgesture still do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the first gesturerecognition criteria to be met because if the contact stayed below therespective intensity threshold until an end of the gesture (e.g., aswipe gesture with a contact that does not increase to an intensityabove the respective intensity threshold), the gesture would have beenrecognized by the first gesture recognition criteria as a swipe gesture.As such, particular gesture recognition criteria that do not requirethat the intensity of the contact(s) meet a respective intensitythreshold in order for the particular gesture recognition criteria to bemet will (A) in some circumstances ignore the intensity of the contactwith respect to the intensity threshold (e.g. for a tap gesture) and/or(B) in some circumstances still be dependent on the intensity of thecontact with respect to the intensity threshold in the sense that theparticular gesture recognition criteria (e.g., for a long press gesture)will fail if a competing set of intensity-dependent gesture recognitioncriteria (e.g., for a deep press gesture) recognize an input ascorresponding to an intensity-dependent gesture before the particulargesture recognition criteria recognize a gesture corresponding to theinput (e.g., for a long press gesture that is competing with a deeppress gesture for recognition).

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts module 137, e-mail module 140, IM module141, browser module 147, and any other application that needs textinput).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone module138 for use in location-based dialing, to camera module 143 aspicture/video metadata, and to applications that provide location-basedservices such as weather widgets, local yellow page widgets, andmap/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone module 138, video conference module 139,e-mail module 140, or IM module 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and music playermodule 146, workout support module 142 includes executable instructionsto create workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (in sports devices and smartwatches); receive workout sensor data; calibrate sensors used to monitora workout; select and play music for a workout; and display, store andtransmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170(e.g., in operating system 126) and a respective application 136-1(e.g., any of the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 168, and/or microphone 113 (through audiocircuitry 110). Information that peripherals interface 118 receives fromI/O subsystem 106 includes information from touch-sensitive displaysystem 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 1C is a block diagram illustrating a tactile output module inaccordance with some embodiments. In some embodiments, I/O subsystem 106(e.g., haptic feedback controller 161 (FIG. 1A) and/or other inputcontroller(s) 160 (FIG. 1A)) includes at least some of the examplecomponents shown in FIG. 1C. In some embodiments, peripherals interface118 includes at least some of the example components shown in FIG. 1C.

In some embodiments, the tactile output module includes haptic feedbackmodule 133. In some embodiments, haptic feedback module 133 aggregatesand combines tactile outputs for user interface feedback from softwareapplications on the electronic device (e.g., feedback that is responsiveto user inputs that correspond to displayed user interfaces and alertsand other notifications that indicate the performance of operations oroccurrence of events in user interfaces of the electronic device).Haptic feedback module 133 includes one or more of: waveform module 123(for providing waveforms used for generating tactile outputs), mixer 125(for mixing waveforms, such as waveforms in different channels),compressor 127 (for reducing or compressing a dynamic range of thewaveforms), low-pass filter 129 (for filtering out high frequency signalcomponents in the waveforms), and thermal controller 131 (for adjustingthe waveforms in accordance with thermal conditions). In someembodiments, haptic feedback module 133 is included in haptic feedbackcontroller 161 (FIG. 1A). In some embodiments, a separate unit of hapticfeedback module 133 (or a separate implementation of haptic feedbackmodule 133) is also included in an audio controller (e.g., audiocircuitry 110, FIG. 1A) and used for generating audio signals. In someembodiments, a single haptic feedback module 133 is used for generatingaudio signals and generating waveforms for tactile outputs.

In some embodiments, haptic feedback module 133 also includes triggermodule 121 (e.g., a software application, operating system, or othersoftware module that determines a tactile output is to be generated andinitiates the process for generating the corresponding tactile output).In some embodiments, trigger module 121 generates trigger signals forinitiating generation of waveforms (e.g., by waveform module 123). Forexample, trigger module 121 generates trigger signals based on presettiming criteria. In some embodiments, trigger module 121 receivestrigger signals from outside haptic feedback module 133 (e.g., in someembodiments, haptic feedback module 133 receives trigger signals fromhardware input processing module 146 located outside haptic feedbackmodule 133) and relays the trigger signals to other components withinhaptic feedback module 133 (e.g., waveform module 123) or softwareapplications that trigger operations (e.g., with trigger module 121)based on activation of the hardware input device (e.g., a home button).In some embodiments, trigger module 121 also receives tactile feedbackgeneration instructions (e.g., from haptic feedback module 133, FIGS. 1Aand 3 ). In some embodiments, trigger module 121 generates triggersignals in response to haptic feedback module 133 (or trigger module 121in haptic feedback module 133) receiving tactile feedback instructions(e.g., from haptic feedback module 133, FIGS. 1A and 3 ).

Waveform module 123 receives trigger signals (e.g., from trigger module121) as an input, and in response to receiving trigger signals, provideswaveforms for generation of one or more tactile outputs (e.g., waveformsselected from a predefined set of waveforms designated for use bywaveform module 123).

Mixer 125 receives waveforms (e.g., from waveform module 123) as aninput, and mixes together the waveforms. For example, when mixer 125receives two or more waveforms (e.g., a first waveform in a firstchannel and a second waveform that at least partially overlaps with thefirst waveform in a second channel) mixer 125 outputs a combinedwaveform that corresponds to a sum of the two or more waveforms. In someembodiments, mixer 125 also modifies one or more waveforms of the two ormore waveforms to emphasize particular waveform(s) over the rest of thetwo or more waveforms (e.g., by increasing a scale of the particularwaveform(s) and/or decreasing a scale of the rest of the waveforms). Insome circumstances, mixer 125 selects one or more waveforms to removefrom the combined waveform (e.g., the waveform from the oldest source isdropped when there are waveforms from more than three sources that havebeen requested to be output concurrently by tactile output generator167)

Compressor 127 receives waveforms (e.g., a combined waveform from mixer125) as an input, and modifies the waveforms. In some embodiments,compressor 127 reduces the waveforms (e.g., in accordance with physicalspecifications of tactile output generators 167 (FIG. 1A) or 357 (FIG. 3)) so that tactile outputs corresponding to the waveforms are reduced.In some embodiments, compressor 127 limits the waveforms, such as byenforcing a predefined maximum amplitude for the waveforms. For example,compressor 127 reduces amplitudes of portions of waveforms that exceed apredefined amplitude threshold while maintaining amplitudes of portionsof waveforms that do not exceed the predefined amplitude threshold. Insome embodiments, compressor 127 reduces a dynamic range of thewaveforms. In some embodiments, compressor 127 dynamically reduces thedynamic range of the waveforms so that the combined waveforms remainwithin performance specifications of the tactile output generator 167(e.g., force and/or moveable mass displacement limits).

Low-pass filter 129 receives waveforms (e.g., compressed waveforms fromcompressor 127) as an input, and filters (e.g., smooths) the waveforms(e.g., removes or reduces high frequency signal components in thewaveforms). For example, in some instances, compressor 127 includes, incompressed waveforms, extraneous signals (e.g., high frequency signalcomponents) that interfere with the generation of tactile outputs and/orexceed performance specifications of tactile output generator 167 whenthe tactile outputs are generated in accordance with the compressedwaveforms. Low-pass filter 129 reduces or removes such extraneoussignals in the waveforms.

Thermal controller 131 receives waveforms (e.g., filtered waveforms fromlow-pass filter 129) as an input, and adjusts the waveforms inaccordance with thermal conditions of device 100 (e.g., based oninternal temperatures detected within device 100, such as thetemperature of haptic feedback controller 161, and/or externaltemperatures detected by device 100). For example, in some cases, theoutput of haptic feedback controller 161 varies depending on thetemperature (e.g. haptic feedback controller 161, in response toreceiving same waveforms, generates a first tactile output when hapticfeedback controller 161 is at a first temperature and generates a secondtactile output when haptic feedback controller 161 is at a secondtemperature that is distinct from the first temperature). For example,the magnitude (or the amplitude) of the tactile outputs may varydepending on the temperature. To reduce the effect of the temperaturevariations, the waveforms are modified (e.g., an amplitude of thewaveforms is increased or decreased based on the temperature).

In some embodiments, haptic feedback module 133 (e.g., trigger module121) is coupled to hardware input processing module 146. In someembodiments, other input controller(s) 160 in FIG. 1A includes hardwareinput processing module 146. In some embodiments, hardware inputprocessing module 146 receives inputs from hardware input device 145(e.g., other input or control devices 116 in FIG. 1A, such as a homebutton). In some embodiments, hardware input device 145 is any inputdevice described herein, such as touch-sensitive display system 112(FIG. 1A), keyboard/mouse 350 (FIG. 3 ), touchpad 355 (FIG. 3 ), one ofother input or control devices 116 (FIG. 1A), or an intensity-sensitivehome button (e.g., as shown in FIG. 2B or a home button with amechanical actuator as illustrated in FIG. 2C). In some embodiments,hardware input device 145 consists of an intensity-sensitive home button(e.g., as shown in FIG. 2B or a home button with a mechanical actuatoras illustrated in FIG. 2C), and not touch-sensitive display system 112(FIG. 1A), keyboard/mouse 350 (FIG. 3 ), or touchpad 355 (FIG. 3 ). Insome embodiments, in response to inputs from hardware input device 145,hardware input processing module 146 provides one or more triggersignals to haptic feedback module 133 to indicate that a user inputsatisfying predefined input criteria, such as an input corresponding toa “click” of a home button (e.g., a “down click” or an “up click”), hasbeen detected. In some embodiments, haptic feedback module 133 provideswaveforms that correspond to the “click” of a home button in response tothe input corresponding to the “click” of a home button, simulating ahaptic feedback of pressing a physical home button.

In some embodiments, the tactile output module includes haptic feedbackcontroller 161 (e.g., haptic feedback controller 161 in FIG. 1A), whichcontrols the generation of tactile outputs. In some embodiments, hapticfeedback controller 161 is coupled to a plurality of tactile outputgenerators, and selects one or more tactile output generators of theplurality of tactile output generators and sends waveforms to theselected one or more tactile output generators for generating tactileoutputs. In some embodiments, haptic feedback controller 161 coordinatestactile output requests that correspond to activation of hardware inputdevice 145 and tactile output requests that correspond to softwareevents (e.g., tactile output requests from haptic feedback module 133)and modifies one or more waveforms of the two or more waveforms toemphasize particular waveform(s) over the rest of the two or morewaveforms (e.g., by increasing a scale of the particular waveform(s)and/or decreasing a scale of the rest of the waveforms, such as toprioritize tactile outputs that correspond to activations of hardwareinput device 145 over tactile outputs that correspond to softwareevents).

In some embodiments, as shown in FIG. 1C, an output of haptic feedbackcontroller 161 is coupled to audio circuitry of device 100 (e.g., audiocircuitry 110, FIG. 1A), and provides audio signals to audio circuitryof device 100. In some embodiments, haptic feedback controller 161provides both waveforms used for generating tactile outputs and audiosignals used for providing audio outputs in conjunction with generationof the tactile outputs. In some embodiments, haptic feedback controller161 modifies audio signals and/or waveforms (used for generating tactileoutputs) so that the audio outputs and the tactile outputs aresynchronized (e.g., by delaying the audio signals and/or waveforms). Insome embodiments, haptic feedback controller 161 includes adigital-to-analog converter used for converting digital waveforms intoanalog signals, which are received by amplifier 163 and/or tactileoutput generator 167.

In some embodiments, the tactile output module includes amplifier 163.In some embodiments, amplifier 163 receives waveforms (e.g., from hapticfeedback controller 161) and amplifies the waveforms prior to sendingthe amplified waveforms to tactile output generator 167 (e.g., any oftactile output generators 167 (FIG. 1A) or 357 (FIG. 3 )). For example,amplifier 163 amplifies the received waveforms to signal levels that arein accordance with physical specifications of tactile output generator167 (e.g., to a voltage and/or a current required by tactile outputgenerator 167 for generating tactile outputs so that the signals sent totactile output generator 167 produce tactile outputs that correspond tothe waveforms received from haptic feedback controller 161) and sendsthe amplified waveforms to tactile output generator 167. In response,tactile output generator 167 generates tactile outputs (e.g., byshifting a moveable mass back and forth in one or more dimensionsrelative to a neutral position of the moveable mass).

In some embodiments, the tactile output module includes sensor 169,which is coupled to tactile output generator 167. Sensor 169 detectsstates or state changes (e.g., mechanical position, physicaldisplacement, and/or movement) of tactile output generator 167 or one ormore components of tactile output generator 167 (e.g., one or moremoving parts, such as a membrane, used to generate tactile outputs). Insome embodiments, sensor 169 is a magnetic field sensor (e.g., a HallEffect sensor) or other displacement and/or movement sensor. In someembodiments, sensor 169 provides information (e.g., a position, adisplacement, and/or a movement of one or more parts in tactile outputgenerator 167) to haptic feedback controller 161 and, in accordance withthe information provided by sensor 169 about the state of tactile outputgenerator 167, haptic feedback controller 161 adjusts the waveformsoutput from haptic feedback controller 161 (e.g., waveforms sent totactile output generator 167, optionally via amplifier 163).

FIG. 2A illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In this embodiment, as well asothers described below, a user is enabled to select one or more of thegraphics by making a gesture on the graphics, for example, with one ormore fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensities of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 167 for generating tactile outputs for a user of device 100.

FIGS. 2B-2C show exploded views of a first input device suitable for usein the electronic devices shown in FIGS. 1A, 2A, 3 , and/or 4A (e.g., ashome button 204). FIG. 2B shows an example of an intensity-sensitivehome button with capacitive sensors used to determine a range ofintensity values that correspond to force applied to theintensity-sensitive home button. FIG. 2C shows an example of a homebutton with a mechanical switch element. With reference to FIG. 2B, theinput device stack 220 includes a cover element 222 and a trim 224. Inthe illustrated embodiment, the trim 224 completely surrounds the sidesof the cover element 222 and the perimeter of the top surface of thecover element 222. Other embodiments are not limited to thisconfiguration. For example, in one embodiment the sides and/or topsurface of the cover element 222 can be partially surrounded by the trim224. Alternatively, the trim 224 can be omitted in other embodiments.

Both the cover element 222 and the trim 224 can be formed with anysuitable opaque, transparent, and/or translucent material. For example,the cover element 222 can be made of glass, plastic, or sapphire and thetrim 224 may be made of a metal or plastic. In some embodiments, one ormore additional layers (not shown) can be positioned below the coverelement 222. For example, an opaque ink layer can be disposed below thecover element 222 when the cover element 222 is made of a transparentmaterial. The opaque ink layer can conceal the other components in theinput device stack 220 so that the other components are not visiblethrough the transparent cover element 222.

A first circuit layer 226 can be disposed below the cover element 222.Any suitable circuit layer may be used. For example, the first circuitlayer 226 may be a circuit board or a flexible circuit. The firstcircuit layer 226 can include one or more circuits, signal lines, and/orintegrated circuits. In one embodiment, the first circuit layer 226includes a biometric sensor 228. Any suitable type of biometric sensorcan be used. For example, in one embodiment the biometric sensor is acapacitive fingerprint sensor that captures at least one fingerprintwhen a user's finger (or fingers) approaches and/or contacts the coverelement 222.

The first circuit layer 226 may be attached to the bottom surface of thecover element 222 with an adhesive layer 230. Any suitable adhesive canbe used for the adhesive layer. For example, a pressure sensitiveadhesive layer may be used as the adhesive layer 230.

A compliant layer 232 is disposed below the first circuit layer 226. Inone embodiment, the compliant layer 232 includes an opening 234 formedin the compliant layer 232. The opening 234 exposes the top surface ofthe first circuit layer 226 and/or the biometric sensor 228 when thedevice stack 220 is assembled. In the illustrated embodiment, thecompliant layer 232 is positioned around an interior perimeter of thetrim 224 and/or around a peripheral edge of the cover element 222.Although depicted in a circular shape, the compliant layer 232 can haveany given shape and/or dimensions, such as a square or oval. Thecompliant layer 232 is shown as a continuous compliant layer in FIGS. 2Band 2C, but other embodiments are not limited to this configuration. Insome embodiments, multiple discrete compliant layers may be used in thedevice stack 220. Additionally, in some embodiments, the compliant layer232 does not include the opening 234 and the compliant layer 232 extendsacross at least a portion of the input device stack 220. For example,the compliant layer 232 may extend across the bottom surface of thecover element 222, the bottom surface of the first circuit layer 226, ora portion of the bottom surface of the cover element 222 (e.g., aroundthe peripheral edge of the cover element) and the bottom surface of thefirst circuit layer 226.

A second circuit layer 238 is positioned below the first circuit layer226. A flexible circuit and a circuit board are examples of a circuitlayer that can be used in the second circuit layer 238. In someembodiments, the second circuit layer 238 can include a first circuitsection 240 and a second circuit section 242. The first and secondcircuit sections 240, 242 can be electrically connected one anotherother.

The first circuit section 240 can include a first set of one or moreintensity sensor components that are included in an intensity sensor. Insome embodiments, the first circuit section 240 can be electricallyconnected to the first circuit layer 226. For example, when the firstcircuit layer 226 includes a biometric sensor 228, the biometric sensor228 may be electrically connected to the first circuit section 240 ofthe second circuit layer 238.

The second circuit section 242 can include additional circuitry, such assignal lines, circuit components, integrated circuits, and the like. Inone embodiment, the second circuit section 242 may include aboard-to-board connector 244 to electrically connect the second circuitlayer 238 to other circuitry in the electronic device. For example, thesecond circuit layer 238 can be operably connected to a processingdevice using the board-to-board connector 244. Additionally oralternatively, the second circuit layer 238 may be operably connected tocircuitry that transmits signals (e.g., sense signals) received from theintensity sensor component(s) in the first circuit section 240 to aprocessing device. Additionally or alternatively, the second circuitlayer 238 may be operably connected to circuitry that provides signals(e.g., drive signals, a reference signal) to the one or more intensitysensor components in the first circuit section 240.

In some embodiments, the first circuit section 240 of the second circuitlayer 238 may be attached to the bottom surface of the first circuitlayer 226 using an adhesive layer 236. In a non-limiting example, a dieattach film may be used to attach the first circuit section 240 to thebottom surface of the first circuit layer 226.

A third circuit layer 246 is disposed below the first circuit section240 of the second circuit layer 238. The third circuit layer 246 mayinclude a second set of one or more intensity sensor components that areincluded in an intensity sensor. The third circuit layer 246 issupported by and/or attached to a support element 248. In oneembodiment, the support element 248 is attached to the trim 224 toproduce an enclosure for the other components in the device stack 220.The support element 248 may be attached to the trim 224 using anysuitable attachment mechanism.

The first set of one or more intensity sensor components in the firstcircuit section 240 and the second set of one or more intensity sensorcomponents in the third circuit layer 246 together form an intensitysensor. The intensity sensor can use any suitable intensity sensingtechnology. Example sensing technologies include, but are not limitedto, capacitive, piezoelectric, piezoresistive, ultrasonic, and magnetic.

In the examples shown in FIGS. 2B and 2C, the intensity sensor is acapacitive force sensor. With a capacitive force sensor, the first setof one or more intensity sensor components can include a first set ofone or more electrodes 250 and the second set of one or more forcesensor components a second set of one or more electrodes 252. Althoughshown in a square shape in FIGS. 2B and 2C each electrode in the firstand second sets of one or more electrodes 250, 252 can have any givenshape (e.g., rectangles, circles). Additionally, the one or moreelectrodes in the first and second sets 250, 252 may be arranged in anygiven pattern (e.g., one or more rows and one or more columns).

FIGS. 2B and 2C show two electrodes in the first and second sets of oneor more electrodes 250, 252. However, other embodiments are not limitedto this configuration. The first and second sets of one or moreelectrodes 250, 252 may each be a single electrode or multiple discreteelectrodes. For example, if the first set of one or more electrodes is asingle electrode, the second set of one or more electrodes comprisesmultiple discrete electrodes. In some embodiments, the second set of oneor more electrodes can be a single electrode and the first set includesmultiple discrete electrodes. Alternatively, both the first and secondsets of one or more electrodes may each include multiple discreteelectrodes.

Each electrode in the first set of one or more electrodes 250 is alignedin at least one direction (e.g., vertically) with a respective electrodein the second set of one or more electrodes 252 to produce one or morecapacitors. When a force input is applied to the cover element 222(e.g., the input surface of the input device), at least one electrode inthe first set 250 moves closer to a respective electrode in the secondset 252, which varies the capacitance of the capacitor(s). A capacitancesignal sensed from each capacitor represents a capacitance measurementof that capacitor. A processing device (not shown) is configured toreceive the capacitance signal(s) and correlate the capacitancesignal(s) to an amount of intensity applied to the cover element 222. Insome embodiments the force sensor can replace a switch element anddifferent intensity thresholds can be used to determine activationevents.

In some embodiments, such as the embodiment shown in FIG. 2C, a switchelement 254 can be positioned below the support element 248. The switchelement 254 registers a user input when a force input applied to thecover element 222 exceeds a given amount of force (e.g., a forcethreshold associated with closing the distance between the first circuitsection 240 and the third circuit layer 246). Any suitable switchelement can be used. For example, the switch element 254 may be a domeswitch that collapses when the force input applied to the cover element222 exceeds the force threshold. When collapsed, the dome switchcompletes a circuit that is detected by a processing device andrecognized as a user input (e.g., a selection of an icon, function, orapplication). In one embodiment, the dome switch is arranged such thatthe apex of the collapsible dome is proximate to the bottom surface ofthe support plate 248. In another embodiment, the base of thecollapsible dome can be proximate to the bottom surface of the supportplate 248.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments. Similar user interfaces are, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Map;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely examples. For example, in some embodiments, icon 422 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3 ) that is separate from the display 450. Device 300also, optionally, includes one or more contact intensity sensors (e.g.,one or more of sensors 359) for detecting intensity of contacts ontouch-sensitive surface 451 and/or one or more tactile output generators357 for generating tactile outputs for a user of device 300.

Although many of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or a stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” is an input element thatindicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface is the force or pressure (force perunit area) of a contact (e.g., a finger contact or a stylus contact) onthe touch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average or a sum) to determine an estimatedforce of a contact. Similarly, a pressure-sensitive tip of a stylus is,optionally, used to determine a pressure of the stylus on thetouch-sensitive surface. Alternatively, the size of the contact areadetected on the touch-sensitive surface and/or changes thereto, thecapacitance of the touch-sensitive surface proximate to the contactand/or changes thereto, and/or the resistance of the touch-sensitivesurface proximate to the contact and/or changes thereto are, optionally,used as a substitute for the force or pressure of the contact on thetouch-sensitive surface. In some implementations, the substitutemeasurements for contact force or pressure are used directly todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is described in units corresponding to thesubstitute measurements). In some implementations, the substitutemeasurements for contact force or pressure are converted to an estimatedforce or pressure and the estimated force or pressure is used todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is a pressure threshold measured in units ofpressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be readily accessible by the user on a reduced-size devicewith limited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch-screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch-screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

As used in the specification and claims, the term “characteristicintensity” of a contact is a characteristic of the contact based on oneor more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, a value produced by low-pass filtering theintensity of the contact over a predefined period or starting at apredefined time, or the like. In some embodiments, the duration of thecontact is used in determining the characteristic intensity (e.g., whenthe characteristic intensity is an average of the intensity of thecontact over time). In some embodiments, the characteristic intensity iscompared to a set of one or more intensity thresholds to determinewhether an operation has been performed by a user. For example, the setof one or more intensity thresholds may include a first intensitythreshold and a second intensity threshold. In this example, a contactwith a characteristic intensity that does not exceed the first thresholdresults in a first operation, a contact with a characteristic intensitythat exceeds the first intensity threshold and does not exceed thesecond intensity threshold results in a second operation, and a contactwith a characteristic intensity that exceeds the second intensitythreshold results in a third operation. In some embodiments, acomparison between the characteristic intensity and one or moreintensity thresholds is used to determine whether or not to perform oneor more operations (e.g., whether to perform a respective option orforgo performing the respective operation) rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location (e.g.,a drag gesture), at which point the intensity of the contact increases.In this example, the characteristic intensity of the contact at the endlocation may be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmmay be applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The user interface figures described herein optionally include variousintensity diagrams that show the current intensity of the contact on thetouch-sensitive surface relative to one or more intensity thresholds(e.g., a contact detection intensity threshold IT₀, a light pressintensity threshold IT_(L), a deep press intensity threshold IT_(D)(e.g., that is at least initially higher than I_(L)), and/or one or moreother intensity thresholds (e.g., an intensity threshold I_(H) that islower than I_(L))). This intensity diagram is typically not part of thedisplayed user interface, but is provided to aid in the interpretationof the figures. In some embodiments, the light press intensity thresholdcorresponds to an intensity at which the device will perform operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, the deep press intensity thresholdcorresponds to an intensity at which the device will perform operationsthat are different from operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, when acontact is detected with a characteristic intensity below the lightpress intensity threshold (e.g., and above a nominal contact-detectionintensity threshold IT₀ below which the contact is no longer detected),the device will move a focus selector in accordance with movement of thecontact on the touch-sensitive surface without performing an operationassociated with the light press intensity threshold or the deep pressintensity threshold. Generally, unless otherwise stated, these intensitythresholds are consistent between different sets of user interfacefigures.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms in duration (e.g., 40, 100, or 120 ms,depending on the magnitude of the second intensity threshold, with thedelay time increasing as the second intensity threshold increases). Thisdelay time helps to avoid accidental deep press inputs. As anotherexample, for some “deep press” inputs, there is a reduced-sensitivitytime period that occurs after the time at which the first intensitythreshold is met. During the reduced-sensitivity time period, the secondintensity threshold is increased. This temporary increase in the secondintensity threshold also helps to avoid accidental deep press inputs.For other deep press inputs, the response to detection of a deep pressinput does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Example factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

For example, FIG. 4C illustrates a dynamic intensity threshold 480 thatchanges over time based in part on the intensity of touch input 476 overtime. Dynamic intensity threshold 480 is a sum of two components, firstcomponent 474 that decays over time after a predefined delay time p1from when touch input 476 is initially detected, and second component478 that trails the intensity of touch input 476 over time. The initialhigh intensity threshold of first component 474 reduces accidentaltriggering of a “deep press” response, while still allowing an immediate“deep press” response if touch input 476 provides sufficient intensity.Second component 478 reduces unintentional triggering of a “deep press”response by gradual intensity fluctuations of in a touch input. In someembodiments, when touch input 476 satisfies dynamic intensity threshold480 (e.g., at point 481 in FIG. 4C), the “deep press” response istriggered.

FIG. 4D illustrates another dynamic intensity threshold 486 (e.g.,intensity threshold I_(D)). FIG. 4D also illustrates two other intensitythresholds: a first intensity threshold I_(H) and a second intensitythreshold I_(L). In FIG. 4D, although touch input 484 satisfies thefirst intensity threshold I_(H) and the second intensity threshold I_(L)prior to time p2, no response is provided until delay time p2 haselapsed at time 482. Also in FIG. 4D, dynamic intensity threshold 486decays over time, with the decay starting at time 488 after a predefineddelay time p1 has elapsed from time 482 (when the response associatedwith the second intensity threshold I_(L) was triggered). This type ofdynamic intensity threshold reduces accidental triggering of a responseassociated with the dynamic intensity threshold I_(D) immediately after,or concurrently with, triggering a response associated with a lowerintensity threshold, such as the first intensity threshold I_(H) or thesecond intensity threshold I_(L).

FIG. 4E illustrate yet another dynamic intensity threshold 492 (e.g.,intensity threshold I_(D)). In FIG. 4E, a response associated with theintensity threshold I_(L) is triggered after the delay time p2 haselapsed from when touch input 490 is initially detected. Concurrently,dynamic intensity threshold 492 decays after the predefined delay timep1 has elapsed from when touch input 490 is initially detected. So adecrease in intensity of touch input 490 after triggering the responseassociated with the intensity threshold I_(L), followed by an increasein the intensity of touch input 490, without releasing touch input 490,can trigger a response associated with the intensity threshold I_(D)(e.g., at time 494) even when the intensity of touch input 490 is belowanother intensity threshold, for example, the intensity threshold I_(L).

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold IT_(L) to an intensity betweenthe light press intensity threshold IT_(L) and the deep press intensitythreshold IT_(D) is sometimes referred to as a “light press” input. Anincrease of characteristic intensity of the contact from an intensitybelow the deep press intensity threshold IT_(D) to an intensity abovethe deep press intensity threshold IT_(D) is sometimes referred to as a“deep press” input. An increase of characteristic intensity of thecontact from an intensity below the contact-detection intensitythreshold IT₀ to an intensity between the contact-detection intensitythreshold IT₀ and the light press intensity threshold IT_(L) issometimes referred to as detecting the contact on the touch-surface. Adecrease of characteristic intensity of the contact from an intensityabove the contact-detection intensity threshold IT₀ to an intensitybelow the contact-detection intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments, IT₀ is greaterthan zero. In some illustrations a shaded circle or oval is used torepresent intensity of a contact on the touch-sensitive surface. In someillustrations, a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments, described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., the respective operation is performed on a“down stroke” of the respective press input). In some embodiments, thepress input includes an increase in intensity of the respective contactabove the press-input intensity threshold and a subsequent decrease inintensity of the contact below the press-input intensity threshold, andthe respective operation is performed in response to detecting thesubsequent decrease in intensity of the respective contact below thepress-input threshold (e.g., the respective operation is performed on an“up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., the respective operationis performed on an “up stroke” of the respective press input).Similarly, in some embodiments, the press input is detected only whenthe device detects an increase in intensity of the contact from anintensity at or below the hysteresis intensity threshold to an intensityat or above the press-input intensity threshold and, optionally, asubsequent decrease in intensity of the contact to an intensity at orbelow the hysteresis intensity, and the respective operation isperformed in response to detecting the press input (e.g., the increasein intensity of the contact or the decrease in intensity of the contact,depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting: an increase in intensityof a contact above the press-input intensity threshold, an increase inintensity of a contact from an intensity below the hysteresis intensitythreshold to an intensity above the press-input intensity threshold, adecrease in intensity of the contact below the press-input intensitythreshold, or a decrease in intensity of the contact below thehysteresis intensity threshold corresponding to the press-inputintensity threshold. Additionally, in examples where an operation isdescribed as being performed in response to detecting a decrease inintensity of a contact below the press-input intensity threshold, theoperation is, optionally, performed in response to detecting a decreasein intensity of the contact below a hysteresis intensity thresholdcorresponding to, and lower than, the press-input intensity threshold.As described above, in some embodiments, the triggering of theseresponses also depends on time-based criteria being met (e.g., a delaytime has elapsed between a first intensity threshold being met and asecond intensity threshold being met).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with adisplay, a touch-sensitive surface, and (optionally) one or more sensorsto detect intensities of contacts with the touch-sensitive surface.

FIGS. 5A1-5A7 illustrate example user interfaces for displayingdifferent user interfaces and/or locking the device in response todifferent activations of a button (e.g., a combined physical home/lockbutton) in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIGS. 6A-6E. For convenience of explanation,some of the embodiments will be discussed with reference to operationsperformed on a device with a touch-sensitive display system 112. In suchembodiments, the focus selector is, optionally: a respective finger orstylus contact, a representative point corresponding to a finger orstylus contact (e.g., a centroid of a respective contact or a pointassociated with a respective contact), or a centroid of two or morecontacts detected on the touch-sensitive display system 112. However,analogous operations are, optionally, performed on a device with adisplay 450 and a separate touch-sensitive surface 451 in response todetecting the contacts on the touch-sensitive surface 451 whiledisplaying the user interfaces shown in the figures on the display 450,along with a focus selector.

For convenience of explanation, some of the embodiments will bediscussed with reference to operations performed on a device with amechanical slider button (e.g., button 501). In FIGS. 5A1-5A7, thebutton (e.g., button 501) is shown as a mechanical slider button,located on the side of device 100, which can be pressed in, moved up,and/or moved down. Although not shown in FIGS. 5A1-5A7, in someembodiments, the button 501 is a mechanical button at another locationon device 100 (e.g., on the top of device 100, on the face of device100, etc.), a virtual button (e.g., a virtual home button on touchscreen 112), or a solid-state button (e.g., a solid state home buttonlocated below touch screen 112). Analogous operations are, optionally,performed on a device with an alternative button. In some embodiments,button 501 in FIGS. 5A1-5A7 replaces home button 204 and/or push button206 of device 100 in FIG. 4A.

FIG. 5A1 illustrates displaying the home screen without locking thedevice, or locking the device, depending on whether a second activationof a button 501 is detected after the initial activation of the button501. In addition, FIG. 5A1 illustrates displaying the home screen beforelocking the device or skipping display of the home screen before lockingthe device, depending on whether the second activation of the button 501is detected within a threshold time T of the initial activation of thebutton 501. As shown in FIG. 5A1, device 100 initially displays anapplication user interface (e.g., user interface 502). First, as shownin path “1” to the lock screen (e.g., user interface 506), when a firstclick and second click are detected on the button 501 within time T,device 100 replaces display of the application user interface (e.g.,user interface 502) with display of the lock screen (e.g., userinterface 506), without displaying the home screen. Alternatively, whena first click is detected on the button 501 and a second click is notdetected with time T, device 100 replaces display of the applicationuser interface (e.g., user interface 502) with display of the homescreen (e.g., user interface 504). Then, as shown in path “2” to thelock screen (e.g., user interface 506), when the second click on thebutton 501 is detected after time T, device 100 replaces display of thehome screen (e.g., user interface 504) with display of the lock screen(e.g., user interface 506).

FIG. 5A2 illustrates unlocking device 100 to display the most recentlydisplayed user interface prior to locking. If device 100 was lockedthrough path “1” in FIG. 5A1 (e.g., from user interface 502), then whenunlocking device 100 from user interface 506, user interface 502 isdisplayed. Alternatively, if device 100 was locked through path “2” inFIG. 5A2 (e.g., from user interface 504), then when unlocking device 100from user interface 506, user interface 504 is displayed.

FIG. 5A3 illustrates initiating a process to turn off device 100 inresponse to a long press on the button 501 (e.g., when liftoff of acontact on the button 501 is detected after a long-press time threshold,TLP). As shown in FIG. 5A3, while device 100 displays the applicationuser interface (e.g., user interface 502), when the button 501 ispressed for at least TLP, device 100 initiates a process to turn off thedevice (e.g., by displaying user interface 508, a confirmation requestfor the user to confirm power off). Although not shown here, in someembodiments, when the button 501 is pressed for at least TLP, device 100is turned off immediately, without first displaying user interface 508.

FIG. 5A4 illustrates displaying a prior application in response to amovement input on the button 501. In one example, while device 100displays an application user interface (e.g., user interface 502 of afirst application), contact 511 slides the button 501 upward along apredefined track, and in response, device 100 replaces the applicationuser interface with another user interface (e.g., user interface 510 ofa second application that was active on device 100 immediately prior tothe first application). In another example, while device 100 displaysthe application user interface (e.g., user interface 502 of the firstapplication), contact 513 slides the button 501 downward along apredefined track, and in response, device 100 replaces the applicationuser interface with another user interface (e.g., user interface 512 ofa third application that was active on device 100 immediately prior tothe second application). Although not shown here, in some embodiments,when contact 513 slides the button 501 downward, device 100 ceases todisplay the current user interface and displays the home screen.

FIG. 5A5 illustrates displaying the home screen (e.g., user interface504), displaying a previous application (e.g., user interface 510), ordisplaying an application-switching user interface (e.g., user interface514), depending on different activations of the button 501. As shown inFIG. 5A5, device 100 initially displays an application user interface(e.g., user interface 502). When a press input is detected on the button501, device 100 replaces display of the application user interface(e.g., user interface 502) with display of the home screen (e.g., userinterface 504). Alternatively, when a slide input is detected on thebutton 501, device 100 replaces display of the application userinterface (e.g., user interface 502) with display of a previousapplication (e.g., user interface 510). In yet another alternative, whena slide and hold input (or, alternatively, a press and hold input) isdetected on the button 501, device 100 replaces display of theapplication user interface (e.g., user interface 502) with display of anapplication-switching user interface (e.g., user interface 514).

FIG. 5A6 illustrates displaying a preview of an application whenstarting an activation of the button 501 and then displaying theapplication when the activation of the button 501 is completed. As shownin FIG. 5A6, device 100 is initially in a locked state (e.g., with thescreen turned off). When an initial portion of an input is detected onthe button 501 (e.g., an initial portion of a slide input upward on thebutton 501), device 100 displays a preview of the last activeapplication on the device (e.g., preview user interface 509). When theinput is completed on the button 501 (e.g., the slide input on button501 is completed (e.g., the button has reached a threshold positionalong the slider track) before the button is released), device 100replaces the preview of the last active application (e.g., preview userinterface 509) with the last active application (e.g., user interface510). On the other hand, if the input is not completed on the button 501(e.g., the slide input on button 501 is not completed (e.g., the buttonhas not reached a threshold position along the slider track) before thebutton is released), device 100 ceases to display the preview of thelast active application (e.g., preview user interface 509) and returnsto the locked state (e.g., with the screen turned off).

Alternatively, FIG. 5A7 illustrates displaying a preview of a lockscreen when starting an activation of the button 501 and then displayingthe lock screen when the activation of the button 501 is completed. Asshown in FIG. 5A7, device 100 is initially in a locked state (e.g., withthe screen turned off). When an initial portion of an input is detectedon the button 501 (e.g., an initial portion of a slide input upward onthe button 501), device 100 displays a preview of the lock screen (e.g.,preview user interface 505). When the input is completed on the button501 (e.g., the slide input on button 501 is completed), device 100replaces the preview of the lock screen (e.g., preview user interface505) with the lock screen (e.g., user interface 506). On the other hand,if the input is not completed on the button 501 (e.g., the slide inputon button 501 is not completed), device 100 ceases to display thepreview of the lock screen (e.g., preview user interface 505) andreturns to the locked state (e.g., with the screen turned off).

FIGS. 5B1-5B22 illustrate example user interfaces for displaying a dockand/or the home screen of a device in response to a multi-stage gesturein accordance with some embodiments. The user interfaces in thesefigures are used to illustrate the processes described below, includingthe processes in FIGS. 7A-7C. For convenience of explanation, some ofthe embodiments will be discussed with reference to operations performedon a device with a touch-sensitive display system 112. In suchembodiments, the focus selector is, optionally: a respective finger orstylus contact, a representative point corresponding to a finger orstylus contact (e.g., a centroid of a respective contact or a pointassociated with a respective contact), or a centroid of two or morecontacts detected on the touch-sensitive display system 112. However,analogous operations are, optionally, performed on a device with adisplay 450 and a separate touch-sensitive surface 451 in response todetecting the contacts on the touch-sensitive surface 451 whiledisplaying the user interfaces shown in the figures on the display 450,along with a focus selector.

FIGS. 5B1-5B9 illustrate opening an application from the home screen andthen displaying a dock (e.g., a container that includes a predefined setof application launch icons and that is usually displayed at the bottomportion of the home screen) and/or the home screen of a device inresponse to detecting a multi-stage gesture. As shown in FIGS. 5B4-5B9,the dock is displayed when the multi-stage gesture meets a firstmovement threshold (e.g., a short swipe up) and the home screen isdisplayed when the multi-stage gesture meets a second movement thresholdthat is greater than the first movement threshold (e.g., a longer and/orfaster swipe up).

In FIGS. 5B1-5B3, device 100 detects an input on the messagingapplication launch icon 524, such as a tap gesture by contact 518, whichlaunches the messaging application (e.g., user interface 520, FIG. 5B3).

FIGS. 5B4-5B9 illustrate movement of a contact 522 (e.g., in a swipegesture) from the bottom edge of device 100 and across touch screen 112in an upward direction. In FIGS. 5B4-5B6, as contact 522 moves upward,dock 540 moves onto user interface 520 with movement of contact 522. InFIGS. 5B7-5B9, as movement of contact 522 continues to move upward, thehome screen (e.g., user interface 504) slides in behind dock 540 andreplaces display of the messaging application (e.g., user interface520). In FIGS. 5B4-5B6, when dock 540 is overlaid over the messagingapplication, dock 540 is semi-transparent, and in FIGS. 5B7-5B9, whendock 540 is overlaid over the home screen, dock 540 is opaque. In FIG.5B9, when dock 540 is overlaid on the home screen, the applicationlaunch icons in dock 540 are updated to include the recently usedapplication on the device (e.g., the messaging application), inaccordance with some embodiments.

FIG. 5B10 illustrates an example of a control center user interfaceobject 542 that is overlaid on a portion of the home screen (e.g., userinterface 504). In the example of FIG. 5B10, the control center userinterface object 542 includes a standard set of controls for controllingdifferent functions of the device 100 (e.g., controls for turning on/offairplane mode, WiFi, Bluetooth, do-not-disturb mode, a screen brightnessslider, etc.). In some embodiments, control center user interface object542 is displayed when the multi-stage gesture meets a third movementthreshold that is greater than the second movement threshold (e.g., aneven longer and/or faster swipe up than the gesture to display the homescreen). In some embodiments, control center user interface object 542is displayed in response to another swipe gesture, such as a swipegesture similar or identical to the swipe gesture by contact 522, afterhome screen (e.g., user interface 504) is displayed.

FIG. 5B11 illustrates an alternative example of a control center userinterface object 544 that is overlaid on a portion of the home screen(e.g., user interface 504). In the example of FIG. 5B11, the controlcenter user interface object 544 includes the standard set of controlsfor controlling different functions of the device 100 (e.g., likecontrol center user interface object 542, FIG. 5B10), and control centeruser interface object 544 also includes a row for the dock. In someembodiments, control center user interface object 544 is displayed whenthe multi-stage gesture meets a third movement threshold that is greaterthan the second movement threshold (e.g., an even longer and/or fasterswipe up than the gesture to display the home screen). In someembodiments, control center user interface object 544 is displayed inresponse to another swipe gesture, such as a swipe gesture similar oridentical to the swipe gesture by contact 522, after home screen (e.g.,user interface 504) is displayed.

FIG. 5B12 illustrates an example of a control center user interfaceobject 546 that is overlaid on a portion of an application userinterface (e.g., user interface 504 of a messaging application). In theexample of FIG. 5B12, the control center user interface object 546includes the standard set of controls for controlling differentfunctions of the device 100 (e.g., like control center user interfaceobject 542, FIG. 5B10), and control center user interface object 546also includes a row for the dock. In some embodiments, the dock isdisplayed when the multi-stage gesture meets a first movement threshold(e.g., a short swipe up) and the control center user interface object546 is displayed when the multi-stage gesture meets a third movementthreshold that is greater than the first movement threshold (e.g., alonger and/or faster swipe up). In some embodiments, control center userinterface object 546 is displayed in response to another swipe gesture,such as a swipe gesture similar or identical to the swipe gesture bycontact 522, after dock 540 is displayed.

FIGS. 5B13-5B15 illustrate displaying an application user interface(e.g., user interface 520) with dock 540 (e.g., after contact 522-clifts off from device 100 in FIG. 5B6), and in response to movement of acontact 548 (e.g., in a swipe gesture) from the bottom edge of device100 and across touch screen 112 in an upward direction, replacingdisplay of the application user interface 520 with display of the homescreen (e.g., user interface 504), in accordance with some embodiments.

FIGS. 5B15-5B17 illustrate displaying the home screen (e.g., userinterface 504), and in response to movement of a contact 550 (e.g., in aswipe gesture) across touch screen 112 in a downward direction,replacing display of the home screen (e.g., user interface 504) withdisplay of the user interface of the last active application on thedevice (e.g., user interface 520). As shown in FIG. 5B17, in someembodiments, when the user interface of the last active application isdisplayed in response to a downward swipe gesture, dock 540 is notdisplayed overlaid on the user interface of the last active application(e.g., user interface 520). In some embodiments, when the user interfaceof the last active application is displayed in response to a downwardswipe gesture, dock 540 remains displayed and is overlaid on the userinterface of the last active application (e.g., user interface 520).

FIGS. 5B18-5B20 illustrate displaying the home screen (e.g., userinterface 504), and in response to movement of a contact 552 (e.g., in aswipe gesture) across touch screen 112 in an upward direction, replacingdisplay of the home screen (e.g., user interface 504) with display ofthe user interface of the last active application on the device (e.g.,user interface 520). As shown in FIG. 5B20, in some embodiments, whenthe user interface of the last active application is displayed inresponse to an upward swipe gesture, dock 540 is displayed (e.g., with asemi-transparent appearance) overlaid on the user interface of the lastactive application (e.g., user interface 520).

FIGS. 5B20-5B22 illustrate displaying an application user interface(e.g., user interface 520) with dock 540, and in response to movement ofa contact 554 (e.g., in a swipe gesture) across touch screen 112 in adownward direction, ceasing to display the dock.

FIGS. 5C1-5C50 illustrate example user interfaces for displaying anon-demand virtual home button and activating the virtual home button todisplay the home screen in response to a continuous gesture inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses in FIGS. 8A-8D. For convenience of explanation, some of theembodiments will be discussed with reference to operations performed ona device with a touch-sensitive display system 112. In such embodiments,the focus selector is, optionally: a respective finger or styluscontact, a representative point corresponding to a finger or styluscontact (e.g., a centroid of a respective contact or a point associatedwith a respective contact), or a centroid of two or more contactsdetected on the touch-sensitive display system 112. However, analogousoperations are, optionally, performed on a device with a display 450 anda separate touch-sensitive surface 451 in response to detecting thecontacts on the touch-sensitive surface 451 while displaying the userinterfaces shown in the figures on the display 450, along with a focusselector.

FIGS. 5C1-5C9 illustrate opening an application from the home screen andthen displaying a dock (e.g., a container that includes a predefined setof application launch icons and that is usually displayed at the bottomportion of the home screen) that includes a home button and activatingthe home button. As shown in FIGS. 5C4-5C9, the dock with the homebutton is displayed when a contact meets home-button-display criteria(e.g., the contact moves from the bottom edge upward beyond a thresholdposition on the display) and the home screen is displayed when thecontact meets display-home criteria (e.g., a characteristic intensity ofthe contact increases above an intensity threshold after the upwardmovement of the contact).

In FIGS. 5C1-5C3, device 100 detects an input on the messagingapplication launch icon 524, such as a tap gesture by contact 555, whichlaunches the messaging application (e.g., user interface 520, FIG. 5C3).

FIGS. 5C4-5C7 illustrate movement of a contact 556 (e.g., in a swipegesture) from the bottom edge of device 100 and across touch screen 112in an upward direction. As contact 556 moves upward, dock 558 (with homebutton 559) moves onto user interface 520 with movement of contact 556.

When device 100 detects that the intensity of contact 556 (e.g., contact556-e in FIG. 5C8) exceeds an intensity threshold (e.g., the light pressintensity threshold IT_(L)), the home screen (e.g., user interface 504,FIG. 5C9) is displayed. In this example, contact 556-e (in FIG. 5C8)exceeds the intensity threshold while on home button 559 to activate thehome button 559.

FIGS. 5C9-5C16 illustrate opening an application from the home screenand then displaying a dock that includes a home button and activatingthe home button. As shown in FIGS. 5C12-5C16, the dock with the homebutton is displayed when a contact meets home-button-display criteria(e.g., the contact moves from the bottom edge upward beyond a thresholdposition on the display) and the home screen is displayed when thecontact meets display-home criteria (e.g., a characteristic intensity ofthe contact increases above an intensity threshold after the upwardmovement of the contact, even if the contact is not on the home button).

In FIGS. 5C9-5C11, device 100 detects an input on the messagingapplication launch icon 524, such as a tap gesture by contact 560, whichlaunches the messaging application (e.g., user interface 520, FIG.5C11).

FIGS. 5C12-5C14 illustrate movement of a contact 562 (e.g., in a swipegesture) from the bottom edge of device 100 and across touch screen 112in an upward direction. As contact 562 moves upward, dock 558 (with homebutton 559) moves onto user interface 520 with movement of contact 562.

When device 100 detects that the intensity of contact 562 (e.g., contact562-d in FIG. 5C15) exceeds an intensity threshold (e.g., the lightpress intensity threshold IT_(L)), the home screen (e.g., user interface504, FIG. 5C16) is displayed. Note that in this example, contact 562-d(in FIG. 5C15) exceeds the intensity threshold after the contact hasmoved past home button 559. However, in response to the continuousgesture of contact 562 (e.g., swiping up to bring up the home button andpressing without liftoff), device 100 displays the home screen (e.g.,user interface 504, FIG. 5C16), without requiring the contact to be onthe home button to activate it.

FIGS. 5C16-5C24 illustrate opening an application from the home screenand then displaying a dock that includes a home button and activatingthe home button. As shown in FIGS. 5C19-5C24, the dock with the homebutton is displayed when a contact meets home-button-display criteria(e.g., the contact moves from the bottom edge upward beyond a thresholdposition on the display) and the home screen is displayed when thecontact meets display-home criteria (e.g., a characteristic intensity ofthe contact increases above an intensity threshold after the upwardmovement of the contact, even if the home button is not yet fullyrevealed).

In FIGS. 5C16-5C18, device 100 detects an input on the messagingapplication launch icon 524, such as a tap gesture by contact 564, whichlaunches the messaging application (e.g., user interface 520, FIG.5C18).

FIGS. 5C19-5C20 illustrate movement of a contact 566 (e.g., in a swipegesture) from the bottom edge of device 100 and across touch screen 112in an upward direction. As contact 566 moves upward, dock 558 (with homebutton 559) moves onto user interface 520 with movement of contact 566.

When device 100 detects that the intensity of contact 566 (e.g., contact566-c in FIG. 5C21) exceeds an intensity threshold (e.g., the lightpress intensity threshold IT_(L)), the home screen (e.g., user interface504, FIGS. 5C22-5C24) is displayed. FIGS. 5C22-5C23 illustrate ananimated transition of the home screen (e.g., user interface 504)sliding in behind dock 568 to replace display of the messagingapplication (e.g., user interface 520). In some embodiments, as shown inFIGS. 5C22-5C24, home button 559 is not displayed in dock 568 when thehome screen is displayed. Note that in this example, contact 566-c (inFIG. 5C21) exceeds the intensity threshold before home button 559 isfully revealed. However, in response to the continuous gesture ofcontact 566 (e.g., swiping up to bring up the home button and pressingwithout liftoff), device 100 displays the home screen (e.g., userinterface 504, FIG. 5C24), without requiring the home button to be fullyrevealed in order to activate it.

In some embodiments, if the contact 566 (e.g., contact 566-b, FIG. 5C20)lifts off before the home-button-display criteria are met (e.g., contact566 includes an initial upward movement to begin display of the dock,but does not include enough distance and/or speed to meet thehome-button-display criteria to fully reveal the home button), dock 558with home button 559 retracts (e.g., in a reverse of the animatedtransition to display the dock) and only user interface 520 isdisplayed.

FIGS. 5C24-5C32 illustrate opening an application from the home screenand then displaying a dock that includes a home button and activatingthe home button. As shown in FIGS. 5C19-5C24, the dock with the homebutton is displayed when a contact meets home-button-display criteria(e.g., the contact moves from the bottom edge upward to a thresholdposition on the display) and the home screen is displayed in response toa separate input (e.g., a tap input by another contact).

In FIGS. 5C24-5C26, device 100 detects an input on the messagingapplication launch icon 524, such as a tap gesture by contact 569, whichlaunches the messaging application (e.g., user interface 520, FIG.5C26).

FIGS. 5C27-5C29 illustrate movement of a contact 570 (e.g., in a swipegesture) from the bottom edge of device 100 and across touch screen 112in an upward direction. As contact 570 moves upward, dock 558 (with homebutton 559) moves onto user interface 520 with movement of contact 570.In FIG. 5C30, contact 570 lifts off and dock 558 with home button 559remains displayed overlaid on user interface 520.

In FIGS. 5C31-5C32, device 100 detects an input on the home button 559,such as a tap gesture by contact 572, and the home screen (e.g., userinterface 504, FIG. 5C32) is displayed.

FIGS. 5C32-5C40 illustrate opening an application from the home screenand then displaying a dock that includes a home button and performing anoperation in response to a separate input (e.g., a press input byanother contact). As shown in FIGS. 5C35-5C40, the dock with the homebutton is displayed when a first contact meets home-button-displaycriteria (e.g., the contact moves from the bottom edge upward to athreshold position on the display) and in response to detecting a pressinput (e.g., without an initial swipe up) by a second contact (e.g.,after liftoff of the first contact), a preview of a photo is displayed.

In FIGS. 5C32-5C34, device 100 detects an input on the messagingapplication launch icon 524, such as a tap gesture by contact 574, whichlaunches the messaging application (e.g., user interface 520, FIG.5C34).

FIGS. 5C35-5C36 illustrate movement of a contact 576 (e.g., in a swipegesture) from the bottom edge of device 100 and across touch screen 112in an upward direction. As contact 576 moves upward, dock 558 (with homebutton 559) moves onto user interface 520 with movement of contact 576.In FIG. 5C37, contact 570 lifts off and dock 558 with home button 559remains displayed overlaid on user interface 520.

In FIGS. 5C38-5C39, device 100 detects an input on the photo thumbnail579, such as a press input by contact 578-a, and a preview of the photo(e.g., photo preview 581, FIG. 5C39) is displayed. When contact 578lifts off, device 100 ceases to display photo preview 580, and themessaging application (e.g., user interface 520) is displayed (as shownin FIG. 5C40). In contrast to FIGS. 5C9-5C16, where in response to thecontinuous gesture of contact 562 (e.g., swiping up to bring up the homebutton and pressing without liftoff), device 100 displays the homescreen in response to contact 562-d (in FIG. 5C15) exceeding theintensity threshold while on photo 579, in FIG. 5C38, contact 578-a is aseparate contact from the contact that brought up the dock (and not partof a continuous gesture as in FIGS. 5C9-5C16). For illustrativepurposes, the position of contact 578 in FIG. 5C39 is the same as theposition of contact 562 in FIG. 5C15, but because the press inputs bythese contacts are part of different gestures, they produce differentoutcomes.

FIGS. 5C40-5C50 illustrate displaying a dock that includes a homebutton, displaying a control center that includes the dock, andactivating a control in the control center. As shown in FIGS. 5C40-5C47,the dock with the home button is displayed when a contact meetshome-button-display criteria (e.g., the contact includes a swipe up) andthe control center is displayed when the contact meets aswipe-control-center-display criteria (e.g., the contact includes asustained movement that is greater than the home-button-displaycriteria).

FIGS. 5C41-5C44 illustrate movement of a contact 582 (e.g., in a swipegesture) from the bottom edge of device 100 and across touch screen 112in an upward direction. As contact 582 moves upward, dock 558 (with homebutton 559) moves onto user interface 520 with movement of contact 582.

As shown in FIGS. 5C45, when device 100 detects that contact 582continues to swipe up (e.g., above a movement threshold, such as 1/7 ofthe display height) after dock 558 (with home button 559) is displayed,a control center 584 (that optionally, includes dock 558) is displayed,overlaid on user interface 520. In some embodiments, as shown in FIG.5C46, as contact 582 moves upward (e.g., in a continuation of the swipegesture), control center 584 moves onto user interface 520 with movementof contact 582. In FIG. 5C47, contact 582 lifts off and control center584 remains displayed overlaid on user interface 520.

In FIGS. 5C48-5C50, device 100 detects an input on the Wi-Fi controlsetting in control center 584, such as a press input by contact 586-a(in FIG. 5C48), which opens a Wi-Fi settings menu (in FIG. 5C49), and inresponse to the selection to turn off Wi-Fi for one hour (e.g., by liftoff of contact 586-b in FIG. 5C49 on the “Turn off for 1 hour” option),Wi-Fi is turned off (in FIG. 5C50).

FIGS. 6A-6E are flow diagrams illustrating a method 600 of displayingthe home screen without locking the device, or locking the device,depending on different activations of a button in accordance with someembodiments. The method 600 is performed at an electronic device (e.g.,device 300, FIG. 3 , or portable multifunction device 100, FIG. 1A) witha display and a touch-sensitive surface. In some embodiments, theelectronic device includes one or more sensors to detect intensity ofcontacts with the touch-sensitive surface. In some embodiments, thetouch-sensitive surface and the display are integrated into atouch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 600 are, optionally,combined and/or the order of some operations is, optionally, changed.

This method relates to displaying the home screen without locking thedevice, or locking the device, depending on whether a second activationof a button is detected after the initial activation of the button.Specifically, after an initial activation of the button, if a secondactivation of the button is not detected within a threshold amount oftime, the home screen is displayed without locking the device; and if asecond activation of the button is detected within the threshold amountof time, the device is locked (e.g., without displaying the home screenfirst). Responding to different activations of a single button todisplay the home screen without locking the device (e.g., when thebutton is activated a first way) and to lock the device withoutdisplaying the home screen (e.g., when the button is activated a secondway) provides an intuitive and efficient way for the user to accessthese often-used functions and avoids unintended locking of the devicewhen going to the home screen and unnecessary user interface switchingwhen locking the device, thereby enhancing the operability of the deviceand making the user-device interface more efficient (e.g., by helpingthe user to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The device (e.g., device 100, FIG. 5A1), while the device is in anunlocked state, detects (602) a sequence of one or more activations of abutton of the device (e.g., button 501, FIG. 5A1, or in otherembodiments, the button is a virtual home button, a solid-state homebutton, or a mechanical home button) (e.g., a home button of the devicethat, when activated in a predetermined manner (e.g., when pressed for asingle time), dismisses a currently displayed user interface anddisplays a home screen of the device, such as user interface 504, FIG.5A1) that includes at least a first activation of the button (e.g., atap or light press input), wherein the first activation of the button isdetected while a respective application user interface other than a homescreen of the device is displayed on the display (e.g., user interface502, FIG. 5A1) (e.g., a state in which one or more functions that aredisabled in a locked state of the device are enabled). In someembodiments, a locked state of the device is a state in which the deviceis prevented from performing one or more functions such as displaying ahome screen, launching an application, accessing personal informationsuch as a photo library, electronic messages, electronic documents,contact information, etc. In some embodiments, an unlocked state of thedevice is a state in which the device is enabled to perform the one ormore functions that are prevented while in the locked state of thedevice. In some embodiments, the device is restricted to providinglimited access to a class of information in the locked state (e.g.,subjects and/or snippets of recently received electronic messages,photos taken while the device is the locked state, upcoming calendarevents), while the device provides more than the limited access (e.g.,full access) to the class of information in the unlocked state (e.g.,the full content of a larger set of electronic messages, all photosstored on the device, all calendar events stored on the electronicdevice, etc.). In some embodiments, destructive actions that arepermitted in the unlocked state are prevented in the locked state (e.g.,in the locked state, electronic messages, photos, contacts and/orelectronic documents cannot be deleted from the device, while in theunlocked state electronic messages, photos, contacts and/or electronicdocuments can be deleted from the device.) In some embodiments, userauthentication (e.g., biometric authentication such as a fingerprint,facial detection, iris scan or input pattern authentication such as apassword, passcode, or touch input pattern) is required by the device inorder to transition from the locked state to the unlocked state. In someembodiments, the locked state is used to prevent unintentional inputinstead of or in addition to preventing unauthorized access to thedevice and a predefined unlock input is required to unlock the device(e.g., placing a finger on a fingerprint sensor, pressing a hardwarebutton, a swipe on a display, activating an intensity-sensitive inputelement, etc.). The device, in response to detecting the sequence of oneor more activations of the button of the device (604): in accordancewith a determination that the first activation of the button wasdetected without a second activation of the button being detected beforea respective threshold amount of time (e.g., a double-click timethreshold, such as time T in FIG. 5A1) from detecting the firstactivation of the button had elapsed, replaces (e.g., upon expiration ofthe respective threshold amount of time) display of the respectiveapplication user interface (e.g., user interface 502, FIG. 5A1) withdisplay of a home screen of the device (e.g., user interface 504, FIG.5A1) while maintaining the device in the unlocked state (e.g., a singlepress input on the home button causes the home screen to be displayed,as shown in FIG. 5A1); and in accordance with a determination that thefirst activation of the button was detected with a second activation ofthe button being detected before the respective threshold amount of timefrom detecting the first activation of the button had elapsed, switchesthe device from the unlocked state, in which the respective applicationuser interface (e.g., user interface 502, FIG. 5A1) is displayed, to alocked state (e.g., user interface 506, FIG. 5A1) (e.g., a double pressdetected within the double click time threshold causes the device toturn off the screen or lock the screen without first going to the homescreen, as shown in path “1” of FIG. 5A1). In some embodiments,detecting the first activation of the button includes (606) detecting afirst press input on the button (e.g., button 501, FIG. 5A1) that meetsfirst click criteria (e.g., the first click criteria include arequirement that is met when the intensity of contact in the first inputis above a first intensity threshold (e.g., a down-click intensitythreshold). In some embodiments, the first click criteria furtherrequire that the contact in the first activation is substantiallystationary (e.g., the contact moves less than a threshold amount ofmovement) before liftoff of the contact is detected or within athreshold amount of time after initial detection of the contact. In someembodiments, the first click criteria further require that the contactis not maintained for more than a second threshold amount of time (e.g.,the long-press time threshold, such as TLP, as shown in FIG. 5A3) thatis greater than the first threshold amount of time (e.g., thedouble-click time threshold, such as T, as shown in FIG. 5A1). In someembodiments, the first click criteria further require that the intensityof the contact decreases below a second intensity threshold that isequal to or lower (e.g., lighter) than the first intensity thresholdafter the intensity had increased above the first intensity threshold(e.g., when both a down-click and an up-click have been detected).Displaying the home screen of the device in response to a first way ofactivating the button (e.g., with a down click) (and locking the devicein response to a second way of activating the button) enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by eliminating the user's need to find and activate anadditional button/affordance and by helping the user to achieve anintended outcome with the required inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, detecting the second activation of the buttonincludes (608) detecting a second press input on the button (e.g.,button 501, FIG. 5A1) that meets second click criteria. In someembodiments, the second click criteria are the same as the first clickcriteria, or have a lower intensity requirement than the first clickcriteria (e.g., the second press input is a lighter press input than thefirst press input), or have a higher intensity requirement than thefirst click criteria (e.g., the second press input is a harder pressinput than the first press input). In some embodiments, the firstactivation and the second activation of the button are by the samecontinuous contact. In some embodiments, the first activation and thesecond activation of the button are by two separate contacts. In someembodiments, the first click criteria require that both a down-click andan up-click to be detected, and the second click criteria do not requirethe up-click of the second click to be detected. Locking the device inresponse to a second way of activating the button (e.g., with a doublepress or double click) (and displaying the home screen in response to afirst way of activating the button) enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byeliminating the user's need to find and activate an additionalbutton/affordance and by helping the user to achieve an intended outcomewith the required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, switching the device from the unlocked state, inwhich the respective application user interface is displayed, to thelocked state includes (610) switching from displaying the respectiveapplication user interface (e.g., user interface 502, FIG. 5A1) todisplaying a lock screen user interface (e.g., user interface 506, FIG.5A1) without displaying the home screen of the device (e.g., therespective application user interface does not transition to the homescreen before the lock screen is displayed when switching from therespective application user interface to displaying the lock screen userinterface, as shown in path “1” of FIG. 5A1). Locking the device bydisplaying the lock screen user interface without displaying the homescreen of the device improves the visual feedback provided to the user(e.g., by making the device appear more responsive to user input) andenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended outcome with the required inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, switching the device from the unlocked state, inwhich the respective application user interface is displayed, to thelocked state includes (612) turning off the display without displayingthe home screen of the device (e.g., the respective application userinterface does not transition to the home screen before the display isturned off when switching from the respective application user interfaceto turning off the display). Locking the device by turning off thedisplay without displaying the home screen of the device improves thevisual feedback provided to the user (e.g., by making the device appearmore responsive to user input) and enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to achieve an intended outcome with the required inputsand reducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the sequence of one ormore activations of the button of the device (614): in accordance with adetermination that the first activation of the button was detected witha second activation of the button being detected after the respectivethreshold amount of time (e.g., time T, FIG. 5A1) from detecting thefirst activation of the button had elapsed, the device displays the homescreen in response to detecting the first activation of the button, andwhile the home screen of the device is displayed on the display, thedevice switches the device from the unlocked state to the locked statein response to detecting the second activation of the button (e.g., twoseparate clicks on the home button cause the device to display the homescreen after the first click and then go to the locked state (e.g.,displaying a lock screen or turning off the display) after the secondclick, as shown in path “2” of FIG. 5A1). In some embodiments, detectingthe second activation of the button includes detecting the down-click ofthe button without detecting the up-click of the button. In someembodiments, the second activation of the button includes both thedown-click and the up-click of the button. When two separate clicks onthe button are detected, displaying the home screen after the firstclick and locking the device after the second click improves the visualfeedback provided to the user (e.g., by making the device appear moreresponsive to user input) and enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, after the second activation of the button wasdetected and while the device is in the locked state, the device detects(616) a third activation of the button that unlocks the device (e.g., asshown in FIG. 5A2) (e.g., detecting the third activation of the buttonincludes detecting a third press input that meets the first clickcriteria and that meets authentication criteria (e.g., the contactmatches the authentication fingerprint)); in response to detecting thethird activation of the button that unlocks the device: in accordancewith a determination that the second activation of the button wasdetected after the respective threshold amount of time from detectingthe first activation of the button had elapsed (e.g., the home screen ofthe device was displayed immediately prior to the locking of the device,as shown in path “2” of FIG. 5A1), the device unlocks the device todisplay the home screen of the device (e.g., as shown in path “2” ofFIG. 5A2) (e.g., if the user had used a slow double click (that isinterpreted as two separate single click inputs) to lock the device,then, the home screen is displayed upon unlocking by the thirdactivation of the button); and in accordance with a determination thatthe second activation of the button was detected before the respectivethreshold amount of time from detecting the first activation of thebutton had elapsed (e.g., the respective application user interface wasdisplayed immediately prior to the locking of the device, as shown inpath “1” of FIG. 5A1), the device unlocks the device to display therespective application user interface (e.g., as shown in path “1” ofFIG. 5A2) (e.g., if the user had used a fast double click (that isinterpreted as a single one double click input) to lock the device, thenthe user interface of the last active application is displayed uponunlocking by the third activation of the button). Unlocking the deviceto display the most recently displayed user interface (prior to locking)allows the user to quickly get back to the home screen or theapplication without requiring further user input. Performing anoperation when a set of conditions has been met without requiringfurther user input enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome with the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the sequence of one ormore activations of the button of the device (618): in accordance with adetermination that detecting the first activation of the button meetslong-press criteria, wherein the long press criteria require that thefirst activation of the button is maintained for at least a thresholdduration (e.g., a long-press time threshold, such as TLP in FIG. 5A3,that is longer than the double-click time threshold) without a secondactivation being detected in order for the long-press criteria to be met(e.g., the contact is maintained for more than the threshold amount oftime after an intensity of the contact exceeded the first intensitythreshold or when the intensity of the contact is maintained above thefirst intensity threshold for more than the threshold amount of time, ora physical button mechanism is depressed for the threshold duration),the device initiates a process to turn off the device (e.g., as shown inFIG. 5A3) (e.g., turning off the device immediately or displaying aconfirmation request for the user to confirm before turning off thedevice). Turning off the device in response to a third way of activatingthe button (e.g., with a long press) (and displaying the home screen orlocking the device in response to different ways of activating thebutton) enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by eliminating the user's need to findand activate an additional button/affordance and by helping the user toachieve an intended outcome with the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the sequence of one ormore activations of the button of the device (620): the device displaysa beginning of an animated transition from the respective applicationuser interface (e.g., user interface 502, FIG. 5A1) to the home screenof the device (e.g., user interface 504, FIG. 5A1) in response todetecting the first activation of the button (e.g., activation by afirst press input that meets the first click criteria); and afterdisplaying the beginning of the animated transition from the respectiveapplication user interface to the home screen of the device, the devicepauses the animated transition from the respective application userinterface to the home screen of the device, wherein: in accordance witha determination that the second activation of the button was notdetected before the respective threshold amount of time from detectingthe first activation of the button had elapsed, replacing display of therespective application user interface with display of the home screen ofthe device includes continuing the animated transition from therespective application user interface to the home screen of the deviceafter the respective threshold amount of time has elapsed (e.g.,animated transition is resumed when the second click is not detectedwithin the double-click interval); and in accordance with adetermination that the second activation of the button was detectedbefore the respective threshold amount of time from detecting the firstactivation of the button had elapsed, switching the device from theunlocked state, in which the respective application user interface isdisplayed, to the locked state includes locking the device (e.g.,displaying user interface 506, FIG. 5A1) without resuming the animatedtransition (e.g., animated transition is not resumed when the secondclick is detected within the double-click interval). Starting theanimated transition before the sequence of activations of the button iscompletely determined improves the visual feedback provided to the user(e.g., by making the device appear more responsive to user input),enhances the operability of the device, and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended outcome with the required inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the sequence of one ormore activations of the button of the device (622): in accordance with adetermination that the second activation of the button was not detectedbefore the respective threshold amount of time from detecting the firstactivation of the button had elapsed (e.g., time T, FIG. 5A1), replacingdisplay of the respective application user interface (e.g., userinterface 502, FIG. 5A1) with display of the home screen of the device(e.g., user interface 504, FIG. 5A1) includes displaying an animatedtransition from the respective application user interface to the homescreen of the device that starts after the respective threshold amountof time has elapsed (e.g., animated transition is started after thedevice has ascertained that no second click is detected within thedouble-click interval), and in accordance with a determination that thesecond activation of the button was detected before the respectivethreshold amount of time from detecting the first activation of thebutton had elapsed, the device locks the device (e.g., displaying userinterface 506, FIG. 5A1) without displaying the animated transition(e.g., no animated transition is displayed when the second click isdetected within the double-click interval). Displaying an animatedtransition to the home screen (when accessing the home screen) orlocking the device without displaying the animated transition (whenlocking the device) improves the visual feedback provided to the user(e.g., by making the device appear more responsive to user input),enhances the operability of the device, and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended outcome with the required inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the sequence of one ormore activations of the button of the device (624): in accordance with adetermination that detecting the one or more activations of the buttonincludes detecting a first movement input that meets application-togglecriteria (e.g., the application-toggle criteria require that the homebutton is moved along a predefined track by more than a first thresholddistance (e.g., 20 pixels or 5 mms), in order for the application-togglecriteria to be met; or the application-toggle criteria require that acontact moves on the home button in a respective direction by more thana threshold distance in order for the application-toggle criteria to bemet), the device replaces the respective application user interface(e.g., user interface 502, FIG. 5A4) with a second user interface (e.g.,user interface 510, FIG. 5A4) that corresponds to another applicationthat was active on the device immediately prior to an application thatcorresponds to the respective application user interface (e.g., as shownin FIG. 5A4). In some embodiments, detecting the first movement inputincludes detecting movement of the button (e.g., button 501, FIG. 5A4)along a predefined track on the device. For example, the first movementinput slides the home button upward along a predefined track of theslider button (e.g., disposed on an edge of the device that is adjacentto the display) (e.g., as shown by contact 511 in FIG. 5A4). In someembodiments, movement of the button is not necessary, and movement of acontact on the button or along an edge (e.g., a side of the device thatis adjacent to the display) of the device (e.g., a swipe upward along atouch-sensitive (e.g., capacitive) edge of the device) performs the samefunction. In some embodiments, a swipe downward on the button (e.g., asshown by contact 513 in FIG. 5A4) or along the touch-sensitive (e.g.,capacitive) edge of the device causes the device to cease to display thecurrent user interface (e.g., user interface 502, FIG. 5A4) and todisplay another user interface (e.g., user interface 512, FIG. 5A4) orto display the home screen. In some embodiments, the currently displayedapplication user interface shrinks toward its corresponding applicationicon to show the home screen (a reverse of the animation that is playedwhen the application icon is clicked to launch the application), when anupward swipe on the home button or along the touch-sensitive (e.g.,capacitive) edge of the device is detected. Displaying a priorapplication in response to a movement input on the button (anddisplaying another application or displaying the home screen or lockingthe device in response to different ways of activating the button)enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by eliminating the user's need to findand activate an additional button/affordance and by helping the user toachieve an intended outcome with the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, (while displaying the respective user interface(e.g., a user interface other than the home screen, such as userinterface 502, FIG. 5A5) or while the device is in the locked state(e.g., while the screen is turned off or displaying a lock screen userinterface)), the device detects (626) a fourth activation of the button;in response to detecting the fourth activation of the button: inaccordance with a determination that detecting the fourth activation ofthe button includes detecting a fourth input on the button that meetsgo-home criteria, wherein the go-home criteria require that the fourthinput meets first click criteria and that the home screen of the deviceis not displayed when the fourth input is detected, in order for thego-home criteria to be met (e.g., the go-home criteria require that thefourth input is a press input on the home button that is detected whenthe display is off or when a user interface other than the home screenis displayed): the device displays the home screen of the device (e.g.,user interface 504, FIG. 5A5) (and optionally, unlocks the device if thedevice was locked); in accordance with a determination that detectingthe fourth activation of the button includes detecting a fifth input onthe button meets go-to-application criteria, wherein thego-to-application criteria require that the fifth input meets firstmovement criteria (e.g., the go-to-application criteria require thatthat the fifth input is an upward movement of the home button along aslider track of the home button for more than a first thresholddistance, or that the fifth input is an upward movement on the homebutton by more than a threshold distance) in order for thego-to-application criteria to be met: the device displays a userinterface of a last active application on the device (e.g., userinterface 510, FIG. 5A5) (e.g., the application that was activeimmediately prior to the screen being turned off, or the applicationthat was active immediately prior to switching to the application thatcorresponds to the currently displayed user interface, or theapplication that was active immediately prior to switching to the homescreen if the home screen is the currently displayed user interface)(and optionally, unlocks the device if the device was locked). In someembodiments, the go-to-application criteria may also be met with anupward swipe along a touch-sensitive (e.g., capacitive) edge of thedevice for more than a respective threshold distance. In someembodiments, in response to detecting release of the button (e.g., byreducing the intensity of the contact to below a release thresholdintensity, or by lift-off of the contact), or detecting the button beingrestored to its default position, the device maintains display of theuser interface of the last active application. Displaying the homescreen of the device in response to a first way of activating the button(e.g., with a down click) and displaying the last active application onthe device in response to a different way of activating the button(e.g., with a movement input) enhances the operability of the device andmakes the user-device interface more efficient (e.g., by eliminating theuser's need to find and activate an additional button/affordance and byhelping the user to achieve an intended outcome with the required inputsand reducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the fourth activation ofthe button: in accordance with a determination that detecting the fourthactivation of the button includes detecting an initial portion of thefifth input that meets preview criteria, wherein the preview criteriarequire that the initial portion of the fifth input meets secondmovement criteria (e.g., the second movement criteria requires a smallerthreshold movement (e.g., 5 pixels or 2 mms) than the first movementcriteria) in order for the preview criteria to be met, the devicedisplays (628) a preview of the user interface of the last activeapplication (e.g., preview user interface 509, FIG. 5A6) on the device(e.g., displaying at least a portion of a snapshot of the last activeapplication on the device) (if the device is not locked, or optionallyunlocking the device if the device is locked). Displaying a preview ofthe last active application on the device when starting an activation ofthe button that would go to the last active application improves thevisual feedback provided to the user (e.g., by making the device appearmore responsive to user input and permitting the user to decide whetherto continue the current input after seeing the preview) and enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome withthe required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the fourth activation ofthe button: in accordance with a determination that detecting the fourthactivation of the button includes detecting an initial portion of thefifth input that meets preview criteria, wherein the preview criteriarequire that the initial portion of the fifth input meets secondmovement criteria (e.g., the second movement criteria requires a smallerthreshold movement (e.g., 5 pixels or 2 mms) than the first movementcriteria) in order for the preview criteria to be met, the devicedisplays (630) a preview of a lock screen user interface (e.g., previewuser interface 505, FIG. 5A7) if the device is locked (e.g., displayingat least a portion of the lock screen user interface). Displaying apreview of the lock screen user interface when starting an activation ofthe button that would go to the lock screen user interface improves thevisual feedback provided to the user (e.g., by making the device appearmore responsive to user input and allowing the user to decide whether tocontinue the current input after seeing the preview) and enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome withthe required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while displaying the preview, the device detects(632) termination of the fifth input on the button (e.g., detectingrelease of the home button with reduction of intensity of contact belowa respective threshold intensity (e.g., a release intensity threshold orup-click intensity threshold) or with lift-off of the contact); inresponse to detecting the termination of the fifth input on the button:in accordance with a determination that the fifth input meets thepreview criteria and does not meet the go-to-application criteria (e.g.,the fifth input does not meet the first movement criteria), the deviceceases to display the preview (e.g., the preview of the user interfaceof the last active application on the device or the preview of the lockscreen user interface upon termination of the fifth input) upontermination of the fifth input (e.g., as shown by the return arrow touser interface 516 from preview user interface 509 and preview userinterface 505 in FIGS. 5A6 and 5A7, respectively). In some embodiments,in response to detecting the termination of the fifth input on thebutton, in accordance with a determination that the fifth input meetsthe go-to-application criteria after having met the preview criteria,the device ceases to display the preview and displays the user interfaceof the last active application (e.g., user interface 510, FIG. 5A6) orthe lock screen (e.g., user interface 506, FIG. 5A7). Displaying apreview of a user interface when starting an activation of the buttonthat would go to the user interface and ceasing to display the previewwhen activation of the button is not completed improves the visualfeedback provided to the user (e.g., by making the device appear moreresponsive to user input and allowing the user to decide whether tocontinue with the current input after seeing the preview) and enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome withthe required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the termination of thefifth input on the button: in accordance with a determination that thefifth input meets the preview criteria and does not meet thego-to-application criteria, the device turns off (634) the display upontermination of the fifth input (e.g., as shown by the return arrow touser interface 516 from preview user interface 509 and preview userinterface 505 in FIGS. 5A6 and 5A7, respectively). In some embodiments,in response to detecting the termination of the fifth input on thebutton, in accordance with a determination that the fifth input meetsthe go-to-application criteria after having met the preview criteria,the device ceases to display the preview and turns off the display.Turning off the display on the device when activation of the button isnot completed improves the visual feedback provided to the user (e.g.,by making the device appear more responsive to user input and allowingthe user to decide whether to continue the current input after seeingthe preview) and enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome with the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the fourth activation ofthe button: in accordance with a determination that detecting the fourthactivation of the button includes detecting a sixth input that meetsapplication-switching criteria, wherein the application-switchingcriteria require that the sixth input includes a movement input thatmeets the first movement criteria and first duration criteria (e.g., thehome button is held at or beyond the threshold position (e.g., 20 pixelsor 5 mms) away from its default position for more than a thresholdamount of time (e.g., 1 second)) in order for the application-switchingcriteria to be met: optionally, the device ceases to display the userinterface of the last active application (e.g., user interface 502, FIG.5A5); the device displays (636) an application-switching user interface(e.g., user interface 514, FIG. 5A5) that includes representations(e.g., live previews or snapshots that are, optionally, reduced in size)of a currently active application and one or more suspended applicationson the device (and optionally, a representation of the home screen).Displaying an application-switching user interface in response to amovement input on the button that meets movement and duration criteria(and displaying the home screen or locking the device in response todifferent ways of activating the button) enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byeliminating the user's need to find and activate an additionalbutton/affordance and by helping the user to achieve an intended outcomewith the required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 6A-6E have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700 and 800) are also applicable in an analogous manner tomethod 600 described above with respect to FIGS. 6A-6E. For example, thecontacts, gestures, user interface objects, tactile outputs, intensitythresholds, focus selectors, and/or animations described above withreference to method 600 optionally have one or more of thecharacteristics of the contacts, gestures, user interface objects,tactile outputs, intensity thresholds, focus selectors, and/oranimations described herein with reference to other methods describedherein (e.g., methods 700 and 800). For brevity, these details are notrepeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3 ) orapplication specific chips.

The operations described above with reference to FIGS. 6A-6E are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operation 602 and replace/switch operation 604 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

FIGS. 7A-7C are flow diagrams illustrating a method 700 of displaying adock and/or the home screen of a device in response to a multi-stagegesture in accordance with some embodiments. The method 700 is performedat an electronic device (e.g., device 300, FIG. 3 , or portablemultifunction device 100, FIG. 1A) with a display and a touch-sensitivesurface. In some embodiments, the electronic device includes one or moresensors to detect intensity of contacts with the touch-sensitivesurface. In some embodiments, the touch-sensitive surface and thedisplay are integrated into a touch-sensitive display. In someembodiments, the display is a touch-screen display and thetouch-sensitive surface is on or integrated with the display. In someembodiments, the display is separate from the touch-sensitive surface.Some operations in method 700 are, optionally, combined and/or the orderof some operations is, optionally, changed.

This method relates to displaying a dock (e.g., a container thatincludes a predefined set of application launch icons and that isusually displayed at the bottom portion of the home screen) and/or thehome screen of a device in response to detecting a multi-stage gesturein which the dock is displayed when the multi-stage gesture meets afirst movement threshold (e.g., a short swipe up) and the home screen isdisplayed when the multi-stage gesture meets a second movement thresholdthat is greater than the first movement threshold (e.g., a longer and/orfaster swipe up). The gestures to bring up the dock and the home screenare optionally two separate gestures or a single continuous gesture.Providing either the dock or the home screen depending on a movementparameter of a movement input allows the user to arrive at a desireduser interface state (e.g., displaying the dock only or displaying thehome screen) by controlling the movement parameter of a single movementinput. Reducing the number of inputs needed to perform these operations(e.g., displaying the dock or displaying the home screen) enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome withthe required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

The device (e.g., device 100, FIG. 5B1) displays (702) a home screen(e.g., user interface 504, FIG. 5B1) on the display (e.g., touch screen112, FIG. 5B1), wherein the home screen includes a plurality ofapplication launch icons (e.g., application launch icons 524-538, FIG.5B1) that correspond to a plurality of applications that are installedon the device (e.g., the plurality of application launch icons arearranged in a grid on the home screen and, optionally, one or morewidgets are also included on the home screen). While displaying the homescreen, the device detects (704) a first input by a first contact (e.g.,tap gesture by contact 518, FIG. 5B2) on a first application launch icon(e.g., messaging application launch icon 524, FIG. 5B2) that meetsapplication-launch criteria (e.g., the first input is a tap on the firstapplication launch icon, as shown in FIG. 5B2). In response to detectingthe first input on the first application launch icon that meets theapplication-launch criteria (e.g., an input such as a tap input), thedevice replaces (706) the home screen (e.g., user interface 504, FIG.5B2) with a first user interface of a first application that correspondsto the first application launch icon (e.g., user interface 520, FIG.5B3). While displaying the first user interface (e.g., user interface520, FIG. 5B4), the device detects (708) a second input by a secondcontact (e.g., contact 522, FIGS. 5B4-5B9) that includes movement acrossthe display in a first direction (e.g., upward). In response todetecting the second input (710): in accordance with a determinationthat the second input meets dock-display criteria, wherein thedock-display criteria require that the second input includes movement ofthe second contact with a magnitude of a movement parameter (e.g.,distance and/or speed) that is above a first movement threshold (e.g., adistance greater than 1/10 of the screen height, or a speed greater than200 pixels per second) in order for the dock-display criteria to be met,the device displays a user interface object (e.g., dock 540, FIGS.5B5-5B6) overlaid on a portion of the first user interface (e.g., userinterface 520, FIGS. 5B5-5B6), wherein the user interface object (e.g.,a dock) includes a first subset of application launch icons from theplurality of application launch icons (without including a virtual homebutton); and in accordance with a determination that the second inputmeets home-display criteria, wherein the home-display criteria requirethat the second input includes movement of the second contact with amagnitude of the movement parameter (e.g., distance and/or speed) thatis above a second movement threshold (e.g., a distance greater than ⅕ ofthe screen height, or a speed greater than 400 pixels per second) thatis greater than the first movement threshold, the device replacesdisplay of the first user interface (e.g., user interface 520, FIGS.5B7-5B8) with display of the home screen (e.g., user interface 504, FIG.5B9) (e.g., while the user interface object, dock 540 in FIGS. 5B7-5B9,continues to be displayed). In some embodiments, the dock displaycriteria and the home display criteria are met by the same input (e.g.,a swipe input that starts from below or at a bottom edge of thetouch-sensitive display or some other predefined position and that movesin a predefined direction (e.g., upward) for more than a first thresholddistance, such as swipe input by contact 522 in FIGS. 5B4-5B9). In someembodiments, an input meets the dock display criteria but does not meetthe home display criteria (e.g., a swipe input that starts from below orat a bottom edge of the touch-sensitive display or some other predefinedposition and that moves in a predefined direction (e.g., upward) formore than a second threshold distance that is smaller than the firstthreshold distance, such as swipe input by contact 522-a through 522-cin FIGS. 5B4-5B6). In some embodiments, an input meets both the dockdisplay criteria and the home display criteria without meeting thedistance requirement, when the input meets a speed requirement (e.g., aswipe input that starts from below or at a bottom edge of thetouch-sensitive display or some other predefined position and that movesin a predefined direction (e.g., upward) for more than a secondthreshold distance that is smaller than the first threshold distance)with more than a first threshold speed). In some embodiments, a longupward swipe and a short fast flick can both meet the dock displaycriteria and the home-display criteria. In some embodiments, when thesecond input does not meet the dock display criteria, a portion of thedock is, optionally, displayed in response to movement of the secondcontact, but the portion of the dock will cease to be displayed (e.g.,retracted) when the termination of the second input is detected withouthaving met the dock display criteria. In some embodiments, if the secondinput meets the dock display criteria and does not meet the home-displaycriteria, the dock is displayed and the home screen is not displayed(e.g., as shown in FIGS. 5B4-5B6). While the dock is displayed, a thirdinput by a third contact that meets the home-display criteria (e.g., anupward swipe on the dock) can also bring up the home screen from behindthe dock and over the first user interface (e.g., as shown in FIGS.5B13-5B15). In some embodiments, once the dock is concurrently displayedwith the home screen, it becomes part of the home screen and isdismissed with the home screen when a gesture for dismissing the homescreen is detected (e.g., as shown in FIGS. 5B15-5B17).

In some embodiments, displaying the user interface object overlaid onthe portion of the first user interface includes (712) moving the userinterface object (e.g., dock 540, FIGS. 5B5-5B6) onto the portion of thefirst user interface (e.g., user interface 520, FIGS. 5B5-5B6) inaccordance with the movement of the second contact (e.g., contact 522-band 522-c, FIGS. 5B5-5B6) (e.g., the dock slides over the first userinterface at a rate based on movement of the second contact). Forexample, the dock slides on more quickly when the movement of the secondcontact is faster and the dock slides on more slowly when the movementof the second contact is slower. In some embodiments, lift-off of thesecond contact is detected before the dock is fully revealed, and thedock continues to slide in over the first user interface due tosimulated inertia after the lift-off of the second contact is detected.The initial speed of the dock after the lift-off of the second contactis based on the speed of the second contact prior to the lift-off of thesecond contact. Moving the dock over the first user interface at a ratebased on movement of the second contact improves the visual feedbackprovided to the user (e.g., by making the device appear more responsiveto user input), enhances the operability of the device, and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome with the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, replacing display of the first user interface withdisplay of the home screen includes (714): displaying the user interfaceobject overlaid on the portion of the first user interface; anddisplaying an animated transition of the home screen replacing displayof the first user interface while continuing to display the userinterface object (e.g., the dock remains on the display and the homescreen slides in behind the dock) (e.g., as shown in FIGS. 5B5-5B8).Displaying an animated transition of the home screen replacing the firstuser interface while continuing to display the dock improves the visualfeedback provided to the user (e.g., by making the device appear moreresponsive to user input), enhances the operability of the device, andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the animated transition of the home screenreplacing display of the first user interface is (716) displayed at arate in accordance with the movement of the second contact (e.g.,contact 522, FIGS. 5B7-5B9) (e.g., the home screen slides onto thedisplay at a rate based on movement of the second contact). For example,the home screen slides on more quickly when the movement of the secondcontact is faster and the home screen slides on more slowly when themovement of the second contact is slower. In some embodiments, the rateof movement of the home screen is selected to simulate directmanipulation of the home screen, so that the home screen slides onto thedisplay at the same rate as the second contact moves on the display. Insome embodiments, lift-off of the second contact is detected before thehome screen is fully revealed, and the home screen continues to slide inover the first user interface due to simulated inertia after thelift-off of the second contact is detected. In some embodiments,lift-off of the second contact is detected before the home screen isrevealed at all, and the home screen slides in over the first userinterface after the lift-off of the second contact is detected (e.g.,when the second contact has a speed above a predetermined thresholdspeed (e.g., 400 pixels per second) before lift-off). In someembodiments, the initial speed of the home screen sliding in after thelift-off of the second contact is based on the speed of the secondcontact prior to the lift-off of the second contact. In someembodiments, the home screen slides upward relative to the secondcontact (e.g., the home screen moves upward from behind the dock fasterthan the upward movement of the second contact once the dock has beenfully revealed) (e.g., as shown in FIGS. 5B7-5B9). Displaying theanimated transition of the home screen replacing the first userinterface at a rate based on movement of the second contact improves thevisual feedback provided to the user (e.g., by making the device appearmore responsive to user input), enhances the operability of the device,and makes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the second input (718): inaccordance with a determination that the second input meetscontrol-center criteria, wherein the control-center criteria requirethat the second input includes movement of the second contact with amagnitude of the movement parameter (e.g., distance and/or speed) thatis above a third movement threshold (e.g., a distance greater than ⅓ ofthe screen height, or a speed greater than 500 pixels per second) thatis greater than the second movement threshold, the device displays acontrol center user interface object (e.g., control center userinterface object 542, 544, or 546 in FIGS. 5B10-5B12, respectively) thatincludes a plurality of controls for controlling different functions ofthe device (e.g., controls for turning on/off WiFi, Bluetooth,flashlight, do-not-disturb mode, airplane mode, the screen brightnessslider, and other controls which may also be accessed through a settingsuser interface or application on the device). In some embodiments, thecontrol center user interface is overlaid on a portion of the homescreen (e.g., on top of the dock) after replacing display of the firstuser interface with display of the home screen (e.g., as shown in FIG.5B10). The home screen remains displayed when the control center isbrought up over the home screen. In some embodiments, when the movementof the second contact has met the second movement threshold, the homescreen slides in over the first user interface from behind the dock at aspeed that is faster than the movement speed of the second contact, andas the movement of the second contact continues and meets the thirdmovement threshold (e.g., the home screen is fully revealed at thispoint), the control center slides in from the bottom edge of the displayover the dock and then over a portion of the home screen. In someembodiments, if the second input ends after the home screen is revealedand before the third movement threshold is met, the control center canbe brought in from the bottom edge of the display by a third input thatstarts from the below or at the bottom edge of the display, but not froma location above the bottom edge of the display. In some embodiments,the second input with a sustained contact that starts from apredetermined position (e.g., at or below the bottom edge of thedisplay) and moving in a predetermined direction (e.g., upward) can pullup objects in different display layers (e.g., the dock, the home screen,and the control center are all on different display layers (on differentz-layers relative to the surface of the display)) during the course ofits movement, while if separate inputs with separate contacts are topull up these different objects, the inputs have to all start from thepredetermined position (e.g., at or below the bottom edge of thedisplay). Displaying the control center in response to detecting amulti-stage gesture that meets a third movement threshold (where thethird movement threshold is greater than a second movement threshold fordisplaying the home screen, which is greater than a first movementthreshold for displaying the dock) enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byreducing the number of user inputs needed to access the control centerand by helping the user to achieve an intended outcome with the requiredinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the user interface object includes (720) a virtualhome button while the user interface object is overlaid on the portionof the first user interface (e.g., as shown in FIG. 5C7), wherein thevirtual home button, when selected, causes the device to cease todisplay the first user interface and display a home screen of thedevice; and the user interface object ceases to include the virtual homebutton while the user interface object is overlaid on a portion of thehome screen (e.g., as shown in FIGS. 5C22-5C23). In some embodiments, atap input on the virtual home button also causes the first userinterface to be replaced with the display of the home screen if thesecond input only met the dock display criteria and did not meet thehome-display criteria (e.g., as shown in FIGS. 5C27-5C32). Displaying ahome button on the dock if the dock is accessed in an application (e.g.,the first application with the first user interface) and not displayingthe home button on the dock if the dock is accessed in the home screenprovides the additional control option of the home button when needed(e.g., when in an application) and does not clutter the dock with theadditional control option of the home button when not needed (e.g., whenalready on the home screen). Providing control options only when neededreduces clutter on the dock, enhances the operability of the device, andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the user interface object includes (722)application launch icons corresponding to one or more recently usedapplications on the device (e.g., as shown in FIGS. 5B7-5B9, where dock540 in FIG. 5B9 is updated to include the recently used messagingapplication) (e.g., the dock includes the N most recent applicationsused on the device, the dock includes N favorite applications specifiedby the user, or the dock includes a combination of favorite applicationsand recent applications and/or suggested applications). Including one ormore recently used applications on the dock provides improvedaccessibility to applications, enhances the operability of the device,and makes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the user interface object is (724) configurable bya user to include one or more of: a virtual home button, one or morecontrol affordances for controlling respective system or devicesettings, and/or one or more application launch icons. In someembodiments, the device removes one or more of the above from the userinterface object in response to detecting touch-and hold input on aparticular item in the user interface object and a dragging input thatcorresponds to movement of the item out of the user interface objectfollowed by liftoff of the contact from the touch-sensitive surface.Allowing a user to configure the dock provides improved accessibility tocontrol affordances and/or applications of the user's choosing andprovides an efficient way for the user to access often-used functions.Providing improved accessibility enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, while displaying the user interface object, thedevice detects (726) a third input by a third contact (e.g., a swipegesture by contact 548, FIG. 5B14) that meets user interface switchingcriteria, wherein the user interface switching criteria require that thethird input includes movement of the third contact across the displaywith a magnitude of a movement parameter (e.g., distance and/or speed)that is above a third movement threshold (e.g., with more than ⅓ of thescreen height, or with a speed greater than 500 pixels per second, etc.)in order for the user interface switching criteria to be met (in someembodiments, the user interface switching criteria also require that themovement is in the first direction (e.g., upward) and/or that themovement starts from a predetermined position (e.g., at or below thebottom edge of the display); and in response to detecting the thirdinput: in accordance with a determination that a respective applicationuser interface (e.g., that is not the home screen) is displayed when thethird contact is detected, the device replaces display of the respectiveapplication user interface with display of the home screen (e.g., asshown in FIGS. 5B14-5B15) (e.g., the respective application userinterface is reduced in size as the swipe progresses, first to make roomfor the dock and then to make room for the home screen). Replacingdisplay of the application with display of the home screen in responseto detecting another swipe while the dock is displayed provides anefficient way to access the home screen, enhances the operability of thedevice, and makes the user-device interface more efficient (e.g., byhelping the user to achieve an intended outcome with the required inputsand reducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the third input (728): inaccordance with a determination that the home screen is displayed whenthe third contact is detected (e.g., a swipe gesture by contact 552,FIG. 5B19), the device replaces display of the home screen with displayof a user interface of a last active application on the device (e.g., asshown in FIGS. 5B19-5B20) (e.g., the previous application that had beenactive immediately before the home screen was displayed). In someembodiments, in response to a first upward swipe gesture, the homescreen slides down, and UI for the most recently used application comestoward user from bottom edge of the display to occupy the whole screen(e.g., as shown in FIGS. 5B19-5B20), and in response to a next upwardswipe gesture, the home screen slides back up, and the application UIrecedes from screen and toward the bottom of screen (e.g., as shown inFIGS. 5B14-5B15). Replacing display of the home screen with display ofthe last active application in response to detecting another swipe whilethe dock is displayed provides an efficient way to access the mostrecently used application, enhances the operability of the device, andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, while displaying the user interface object, thedevice detects (730) a fourth input by a fourth contact (e.g., swipegesture by contact 554, FIG. 5B21) that meets user interface dismissalcriteria, wherein the user interface dismissal criteria require that thefourth input includes movement of the fourth contact across the displayin a second direction (e.g., downward) that is different from the firstdirection; and in response to detecting the fourth input: in accordancewith a determination that a respective application user interface (e.g.,that is not the home screen) is displayed when the fourth contact isdetected, the device ceases to display the user interface object (e.g.,swipe down while displaying dock to hide dock) while maintaining displayof the respective application user interface (e.g., as shown in FIGS.5B21-5B22). Ceasing to display the dock in response to detecting aninput in a second direction (e.g., a swipe down) while the dock isdisplayed provides an efficient way to dismiss the dock, enhances theoperability of the device, and makes the user-device interface moreefficient (e.g., by reducing the number of inputs needed to perform anoperation and by helping the user to achieve an intended outcome withthe required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the fourth input (732): inaccordance with a determination that the home screen is displayed whenthe fourth contact is detected (e.g., swipe gesture by contact 550, FIG.5B16), the device replaces display of the home screen with display of auser interface of a last active application on the device (e.g., theprevious application that had been active immediately before the homescreen was displayed) (e.g., as shown in FIGS. 5B16-5B17). Replacingdisplay of the home screen with display of the last active applicationin response to detecting an input in a second direction (e.g., a swipedown) while the dock is displayed provides an efficient way to accessthe most recently used application, enhances the operability of thedevice, and makes the user-device interface more efficient (e.g., byreducing the number of inputs needed to perform an operation and byhelping the user to achieve an intended outcome with the required inputsand reducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the fourth input, thedevice ceases (734) to display the user interface object when display ofthe user interface of the last active application has replaced displayof the home screen (e.g., as shown in FIG. 5B17). Ceasing to display thedock when display of the last active application replaces display of thehome screen provides immediate access to the full user interface of theapplication without requiring further user input to dismiss the dock.Performing an operation when a set of conditions has been met withoutrequiring further user input enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, displaying the user interface object (e.g., thedock) includes (736): in accordance with a determination that the userinterface object is overlaid over a portion of the home screen,displaying the user interface object with a first appearance (e.g., thefirst appearance is opaque and blocks the portion of the home screen orforms part of the home screen, as shown in FIG. 5B15); and in accordancewith a determination that the user interface object is overlaid over aportion of the first user interface (e.g., that is not the home screen),displaying the user interface object with a second appearance (whereinthe second appearance allows the portion of the first user interface tobe partially visible from behind the user interface object (e.g., thedock is semi-transparent, as shown in FIG. 5B14)). Displaying the dockwith a first appearance (e.g., opaque) over the home screen anddisplaying the dock with a second appearance (e.g., semi-transparent)over an application user interface provides improved visual feedback tothe user and allows the full user interface of the application to bevisible to the user. Providing improved feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome withthe required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 7A-7C have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 600 and 800) are also applicable in an analogous manner tomethod 700 described above with respect to FIGS. 7A-7C. For example, thecontacts, gestures, user interface objects, tactile outputs, intensitythresholds, focus selectors, and/or animations described above withreference to method 700 optionally have one or more of thecharacteristics of the contacts, gestures, user interface objects,tactile outputs, intensity thresholds, focus selectors, and/oranimations described herein with reference to other methods describedherein (e.g., methods 600 and 800). For brevity, these details are notrepeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3 ) orapplication specific chips.

The operations described above with reference to FIGS. 7A-7C are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, display operation 702, detection operation 704, replaceoperation 706, detection operation 708, and display operation 710 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

FIGS. 8A-8D are flow diagrams illustrating a method 800 of displaying anon-demand virtual home button and activating the virtual home button todisplay the home screen in response to a continuous gesture inaccordance with some embodiments. The method 800 is performed at anelectronic device (e.g., device 300, FIG. 3 , or portable multifunctiondevice 100, FIG. 1A) with a display and a touch-sensitive surface. Insome embodiments, the electronic device includes one or more sensors todetect intensity of contacts with the touch-sensitive surface. In someembodiments, the touch-sensitive surface and the display are integratedinto a touch-sensitive display. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 800 are, optionally,combined and/or the order of some operations is, optionally, changed.

This method relates to displaying an on-demand virtual home button inresponse to detecting an initial movement of an input (e.g., a swipeup), and in response to detecting an increase in the characteristicintensity of the input above an intensity threshold, activating thevirtual home button to display the home screen (e.g., without requiringthe input to be on the virtual home button). Displaying an on-demandvirtual home button and activating the virtual home button to displaythe home screen in response to a continuous gesture provides anefficient way to access the home screen. Reducing the number of inputsneeded to perform an operation enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The device (e.g., device 100, FIG. 5C1) displays (802) a home screen(e.g., user interface 504, FIG. 5C1) on the display (e.g., touch screen112, FIG. 5C1), wherein the home screen includes a plurality ofapplication launch icons (e.g., application launch icons 524-538) thatcorrespond to a plurality of applications that are installed on thedevice (e.g., the plurality of application launch icons are arranged ina grid on the home screen and, optionally, one or more widgets are alsoincluded on the home screen). While displaying the home screen, thedevice detects (804) a first input by a first contact (e.g., tap gestureby contact 555, FIG. 5C2) on a first application launch icon (e.g.,messaging application launch icon 524, FIG. 5C2) that meetsapplication-launch criteria (e.g., the first input is a tap on the firstapplication launch icon, as shown in FIG. 5C2). In response to detectingthe first input on the first application launch icon that meets theapplication-launch criteria (e.g., an input such as a tap input), thedevice replaces (806) the home screen (e.g., user interface 504, FIG.5C2) with a first user interface of a first application that correspondsto the first application launch icon (e.g., user interface 520, FIG.5C3). While displaying the first user interface (e.g., user interface520, FIG. 5C4), the device detects (808) a sequence of one or moreinputs performed by a second contact (e.g., a contact that iscontinuously detected on the touch-sensitive surface during the sequenceof one or more inputs, and that is distinct from the first contact)(e.g., contact 556, FIG. 5C4-5C8). In response to detecting the sequenceof one or more inputs performed by the second contact (810): inaccordance with a determination that the sequence of one or more inputsincludes a second input by the second contact that meetshome-button-display criteria, wherein the home-button-display criteriarequire that the second input includes an initial movement of the secondcontact across the touch-sensitive surface in a first direction (e.g.,upward) in order for the home-button-display criteria to be met, thedevice displays a user interface object (e.g., a dock or a launch padwith application launch icons for a set of preselected applications orfrequently used applications) overlaid on the first user interface(e.g., as shown in FIGS. 5C5-5C7), wherein the user interface objectincludes a home button (e.g., home button 559, FIGS. 5C6-5C7) that isassociated with displaying the home screen of the device (e.g., the homebutton dismisses a currently displayed user interface regardless of whatthat currently displayed user interface is, and displays the homescreen); and in accordance with a determination that the sequence of oneor more inputs includes a third input by the second contact that meetsdisplay-home criteria, wherein the display-home criteria require that acharacteristic intensity of the second contact increases above a firstintensity threshold in order for the display-home criteria to be met(e.g., above IT_(L), as shown in FIG. 5C8), the device replaces displayof the first user interface with display of the home screen (e.g., asshown in FIGS. 5C8-5C9). In some embodiments, the home-button-displaycriteria require that the second input includes an initial movement ofthe second contact with a magnitude of a movement parameter (e.g.,distance and/or speed) that is above a first movement threshold in orderfor the home-button-display criteria to be met. For example, in someembodiments, the home-button-display criteria are met by a swipe inputthat starts from below or at a bottom edge of the touch-sensitivedisplay or some other predefined position and that moves in a predefineddirection (e.g., upward) for more than a first threshold distance (e.g.,1/10 of the display height). In some embodiments, when the second inputmeets a threshold speed requirement (e.g., greater than 200 pixels persecond), the movement requirement can be lowered (e.g., to 1/15 of thedisplay height). For example, in some embodiments, thehome-button-display criteria are also met by a swipe input that startsfrom below or at a bottom edge of the touch-sensitive display or someother predefined position and that moves in a predefined direction(e.g., upward) for more than a second threshold distance (e.g., 1/15 ofthe display height) that is smaller than the first threshold distancewith more than a first threshold speed (e.g., more than 200 pixels persecond). In some embodiments, a long upward swipe and a short fast flickboth meet the home-button-display criteria. In some embodiments, whenthe second input does not meet the home-button-display criteria or thedisplay-home criteria, a portion of the user interface object with thehome button may be displayed in accordance with the movement of thesecond contact, but the portion of the user interface object with thehome button will cease to be displayed (e.g., retracted) when thetermination of the second input (e.g., lift-off of the second contact)is detected without having met either the home-button-display criteriaor the display-home criteria. In some embodiments, if thehome-button-display criteria are met and the display-home criteria arenot meet, the user interface object with the home button remainsdisplayed and a transition to the home screen is not displayed after thelift-off of the second contact is detected. In such a case, while theuser interface object with the home button is displayed, another inputby a separate contact that activates the home button can also bring upthe home screen (e.g., from behind the user interface object and overthe first user interface).

In some embodiments, the display-home criteria further require (812)that the third input includes an initial movement of the second contactacross the touch-sensitive surface in the first direction before thecharacteristic intensity of the second contact increases above the firstintensity threshold in order for the display-home criteria to be met(e.g., as shown in FIGS. 5C4-5C8). For example, the user swipes up fromthe predetermined position (e.g., at or below the bottom edge of thedisplay) to bring up at least a portion of the user interface objectthat includes the virtual home button (e.g., dock 558 with home button559, FIGS. 5C6-5C7), and then presses against the touch-sensitivedisplay to activate the virtual home button without lifting up thefinger from the touch-sensitive display (e.g., as shown in FIG. 5C8). Inresponse to the swipe-press gesture, the home screen replaces the firstuser interface before lift-off of the second contact is detected. Insome embodiments, the device replaces the first user interface with thehome screen after lift-off of the second contact is detected. Displayingthe home screen in response to a swipe-press gesture provides anefficient way to access the home screen, enhances the operability of thedevice, and makes the user-device interface more efficient (e.g., byreducing the number of inputs needed to perform an operation and byhelping the user to achieve an intended outcome with the required inputsand reducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, replacing display of the first user interface withdisplay of the home screen includes (814) starting a transition from thefirst user interface to the home screen before the user interface objectthat includes the home button is fully revealed on the display (e.g., asshown in FIGS. 5C21-5C22). For example, as the user swipes up from thebottom of the touch-sensitive display and after at least a thresholdportion of the user interface object that includes the virtual homebutton is revealed in accordance with the upward movement of the secondcontact (or after at least the second contact has reached a predefinedthreshold position on the display), the transition to display the homescreen can start at any time when the user's input meets the firstintensity threshold, regardless of whether the user interface object orthe home button has been fully revealed at that time (e.g., as shown inFIG. 5C21). In some embodiments, the user interface object that includesthe home button is fully revealed after the transition to the homescreen has already started (e.g., as shown in FIG. 5C23). Starting thetransition from the first user interface to the home screen before theuser interface object that includes the home button is fully revealed onthe display improves the visual feedback provided to the user (e.g., bymaking the device appear more responsive to user input), enhances theoperability of the device, and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome withthe required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the second contact is (816) detected at a firstlocation on the display that corresponds to a display location of afirst user interface object (e.g., photo thumbnail 579, FIG. 5C38) inthe first user interface (e.g., user interface 520, FIG. 5C38) (e.g., anemail item in an email listing user interface or image thumbnail in anchat user interface) when the display-home criteria are met by thesecond input (and optionally, before the first location is occupied bythe home button or the user interface object with the home button). Insome embodiments, while displaying the first user interface and prior todetecting the sequence of one or more inputs performed by the secondcontact: the device detects an input by a third contact that meetspress-object-activation criteria while the third contact is detected atthe first location on the display (e.g., press input by contact 578,FIG. 5C38), wherein the press-object-activation criteria require thatthe input by the third contact does not include an initial movement ofthe third contact that meets the home-button-display criteria and that acharacteristic intensity of the third contact exceeds the firstintensity threshold (e.g., the light press intensity threshold IT_(L)),in order for the press-object-activation criteria to be met; and inresponse to detecting the input by the third contact that meets thepress-object-activation criteria, the device performs an operation thatcorresponds to the first user interface object (e.g., displaying apreview of the object, as shown in FIG. 5C39) (without displaying thehome button or the home screen). In other words, the press input that isdetected at the first location that corresponds to the first userinterface object triggers performance of an operation that correspondsto the first user interface object (e.g., displaying a preview of theobject such as a portion of an email corresponding to the user interfaceobject or menu that corresponds to the first user interface object suchas a quick action menu with a plurality of selectable options that areassociated with the first user interface object) if the user input is apress input without an initial swipe (e.g., as shown in FIGS.5C38-5C39), or triggers display of the home screen if the user input isa press input that is preceded by an initial swipe to bring up the dock(e.g., as shown in FIGS. 5C15-5C16) (even if the dock is not fullyrevealed to cover the first location when the press input is detected,as shown in FIG. 5C21). Performing an operation in response to a pressinput (and displaying the home screen in response to a swipe-pressinput) provides additional control options without cluttering the userinterface with additional displayed controls, enhances the operabilityof the device, and makes the user-device interface more efficient (e.g.,by helping the user to achieve an intended outcome with the requiredinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the display-home criteria require (818) that thehome-button-display criteria are met by the second contact before thecharacteristic intensity of the second contact increases above the firstintensity threshold (e.g., the light press intensity threshold IT_(L))in order for the display-home criteria to be met (e.g., as shown inFIGS. 5C4-5C8). For example, if the home-button-display criteria requirethat an initial movement of the second contact exceed a predeterminedthreshold distance, and/or a threshold position on the display, and/or athreshold speed, and/or start from a predetermined position (e.g., belowthe bottom edge of the display), in order for the home-button-displaycriteria to be met, the display-home criteria include these requirementsand the additional requirement that the characteristic intensity of thesecond contact exceeds the predetermined intensity threshold after thehome-button-display criteria are met. Requiring that thehome-button-display criteria are met before the characteristic intensityof the second contact increases in order for the display-home criteriato be met provides improved feedback to the user (e.g., by displayingthe home button and indicating that pressing harder will cause thedevice to go to the home screen), enhances the operability of thedevice, and makes the user-device interface more efficient (e.g., byhelping the user to achieve an intended outcome with the required inputsand reducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the display-home criteria do not require (820) thatthe home-button-display criteria are met by the second contact beforethe characteristic intensity of the second contact increases above thefirst intensity threshold (e.g., the light press intensity thresholdIT_(L)) in order for the display-home criteria to be met (e.g., as shownin FIGS. 5C19-5C21). For example, if the home-button-display criteriarequire that an initial movement of the second contact to exceed apredetermined threshold distance (e.g., 1/10 of display height), and/ora threshold position on the display (e.g., 1/10 of display height fromthe bottom edge of the display), and/or a threshold speed (e.g., 200pixels per second), and/or start from a predetermined position (e.g.,below the bottom edge of the display), in order for thehome-button-display criteria to be met, the display-home criteria can bemet by a second contact that meets these requirements and the additionalrequirement that the characteristic intensity of the second contactexceeds the predetermined intensity threshold (e.g., the light pressintensity threshold IT_(L)) after the home-button-display criteria aremet. However, the display-home criteria can also be met when the secondcontact does not meet all of the requirements for thehome-button-display criteria, but meets some of the requirements ormeets relaxed versions of some of the requirements in thehome-button-display criteria, as long as the characteristic intensity ofthe second contact exceeds the predetermined intensity threshold (e.g.,as shown in FIG. 5C21). In some embodiments, if the user's input doesnot end in a press input that triggers the display of the home screen(e.g., the user's input does not end with an increase in intensity abovethe required threshold intensity), the user will need to swipe a littlefurther (e.g., 1/15 of screen height) or a little faster (e.g., 300pixels per second) in order to bring up the user interface object thatincludes the home button and have the user interface object and homebutton remain displayed on the screen after lift-off of the secondcontact. Not requiring that the home-button-display criteria are metbefore the characteristic intensity of the second contact increases, butallowing some flexibility in order for the display-home criteria to bemet provides improved feedback and reduces the number of inputs neededto perform an operation (e.g., by displaying the home screen when theinput is close enough to the swipe-press gesture), enhances theoperability of the device, and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended outcome withthe required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the sequence of one ormore inputs performed by the second contact (822): in accordance with adetermination that the sequence of one or more inputs includes thesecond input by the second contact that meets the home-button displaycriteria and does not include the third input by the second contact thatmeets the display-home criteria, the device maintains display of theuser interface object that includes the home button overlaid on thefirst user interface (without replacing display of the first userinterface with the display of the home screen) (e.g., as shown in FIGS.5C27-5C30). For example, when a user swipes up from the bottom edge ofthe screen to bring up the user interface object that includes the homebutton, if the user does not provide a press input that meets theintensity requirement of the home-display criteria, the user interfaceobject that includes the home button remains displayed after lift-off ofthe second contact (e.g., as shown in FIG. 5C30). In some embodiments,the lift-off of the second contact is detected before the user interfaceobject is fully revealed, and the user interface object with the homebutton continues to slide onto the display after the lift-off of thesecond contact with movement due to simulated inertia, and remainsdisplayed after it is fully revealed on the display. Maintaining displayof the user interface object that includes the home button when thesecond contact does not meet display-home criteria improves the visualfeedback provided to the user (e.g., by making the device appear moreresponsive to user input), enhances the operability of the device, andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, while maintaining display of the user interfaceobject that includes the home button, the device detects (824) a fourthinput by a fourth contact on the home button (e.g., the fourth input isa tap on the home button by the third contact after liftoff from thesecond contact, as shown in FIG. 5C31); and in response to detecting thefourth input: the device replaces display of the first user interfacewith display of the home screen (e.g., as shown in FIGS. 5C31-5C32)(e.g., in response to detecting the activation of the virtual homebutton, the device switches from displaying a current user interface todisplaying the home screen). In some embodiments, when the home screenis displayed, the device ceases to display the home button in the userinterface object (e.g., as shown in FIG. 5C32). Displaying the homescreen in response to activation of the virtual home button improves thevisual feedback provided to the user (e.g., by making the device appearmore responsive to user input), enhances the operability of the device,and makes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the sequence of one ormore inputs performed by the second contact (826): in accordance with adetermination that the sequence of one or more inputs includes a fifthinput by the second contact that meets swipe-control-center-displaycriteria, wherein the swipe-control-center-display criteria require thatthe fifth input includes a sustained movement of the second contact witha magnitude of a movement parameter (e.g., distance and/or speed) thatis above a first movement threshold (e.g., 1/7 of display height) afterthe home-button-display criteria have been met in order for theswipe-control-center-display criteria to be met, the device displays acontrol center user interface object (e.g., control center 584, FIG.5C45) overlaid on a portion of the display (e.g., as shown in FIGS.5C45-5C47). In some embodiments, the control center user interfaceobject includes one or more affordances to control one or moreapplications and/or settings on the device. For example, in someembodiments, affordances in the control center user interface objectinclude controls a brightness control, an orientation control, a volumecontrol, a do-not-disturb setting, a Bluetooth setting, a Wi-Fi setting,and/or airplane mode control, and other controls that are alsoaccessible through a device settings user interface or application. Insome embodiments, the control user interface also includes one or morequick launch icons for launching one or more applications without goingto the home screen. In some embodiments, the control center userinterface object is displayed as an extension of the user interfaceobject with the home button. In some embodiments, the control centeruser interface slides in over the user interface object with the homebutton and obscures at least a portion of the user interface object withthe home button. In some embodiments, the control center user interfaceslides in at a rate based on movement of the second contact and isdirectly manipulated by the second contact (e.g., as shown in FIGS.5C45-5C46). In some embodiments, the control center user interfaceovertakes the movement of the second contact in reaching its finalposition, once the second contact has met theswipe-control-center-display criteria. Displaying the control center inresponse to detecting a gesture after displaying the user interfaceobject with the home button enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing thenumber of user inputs needed to access the control center and by helpingthe user to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the display-home criteria require (828) that theswipe-control-center-display criteria are not met before thecharacteristic intensity of the second contact increases above the firstintensity threshold (e.g., the light press intensity threshold IT_(L))in order for the display-home criteria to be met. For example, inresponse to detecting that the characteristic intensity of the secondcontact has increased above the first intensity threshold, the devicestarts the transition from the first user interface to the home screenin accordance with a determination that the home-button-display criteriahave been met and that the swipe-control-center-display criteria havenot been met. In accordance with a determination that both thehome-button-display criteria and the swipe-control-center-displaycriteria have been met, the device does not start the transition fromthe first user interface to the home screen, and optionally, performs afunction associated with the control center user interface (e.g.,activating a control in control center the user interface) in responseto the press input. Displaying the home screen in response to thecharacteristic intensity of the second contact increasing above thefirst intensity threshold only when the swipe-control-center-displaycriteria are not met improves the visual feedback provided to the user(e.g., by making the device appear more responsive to user input),enhances the operability of the device, and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended outcome with the required inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the sequence of one ormore inputs performed by the second contact (830): in accordance with adetermination that the sequence of one or more inputs includes a sixthinput by the second contact, wherein the sixth input includes movementin the first direction after the home-button-display criteria have beenmet and includes lift-off of the second contact: the device displays abeginning of an animated transition to display the control center userinterface object; and in accordance with a determination that the sixthinput by the second contact does not meet theswipe-control-center-display criteria (e.g., sixth input includesmovement beyond the initial movement of the second contact to displaythe dock, but not enough distance and/or speed to meet theswipe-control-center-display criteria to fully reveal the control centeruser interface): the device displays a reverse of the animatedtransition to display the control center user interface object (e.g.,the control center user interface object slides back off of thedisplay); and the device maintains display of the user interface objectthat includes the home button. Displaying an animated transition todisplay the control center user interface object and then reversing theanimated transition if the second contact does not meet theswipe-control-center-display criteria improves the visual feedbackprovided to the user (e.g., by making the device appear more responsiveto user input), enhances the operability of the device, and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended outcome with the required inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the device displays (832) a status bar (e.g., alongthe bottom edge of the display, or next to the upper left or rightcorner of the display) on the display (e.g., the status bar includingstatus information such as the current time, WiFi and cellular signalstrengths, battery level, etc.); while displaying the status bar on thedisplay, the device detects a seventh input by a fifth contact on thestatus bar; and in response to detecting the seventh input by the fifthcontact on the status bar: in accordance with a determination that theseventh input by the fifth contact meets press-control-center-displaycriteria, wherein the press-control-center-display criteria require thata characteristic intensity of the fifth contact increases above thefirst intensity threshold in order for the press-control-center-displaycriteria to be met, the device displays a control center user interfaceobject (e.g., control center 584, FIG. 5C47) overlaid on a portion ofthe display. In some embodiments, in accordance with a determinationthat the seventh input by the fifth contact does not meetpress-control-center-display criteria (e.g., the characteristicintensity of the fifth contact does not increase above the firstintensity threshold), the control center user interface object is notdisplayed. In some embodiments, the control center user interface objectincludes the home button that is associated with displaying the homescreen of the device. In some embodiments, the home button is separatefrom the control center user interface object and is brought up by anupward swipe from the bottom edge of the display (e.g., as describedabove in 810). In some embodiments, the control center user interfaceobject is overlaid on a portion of an application user interface (e.g.,when the application user interface is displayed while detecting theseventh input by the fifth contact on the status bar). In someembodiments, the control center user interface object is overlaid on aportion of the home screen (e.g., when the home screen is displayedwhile detecting the seventh input by the fifth contact on the statusbar). Displaying the control center in response to a force press inputon the status bar enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the number ofuser inputs needed to access the control center and by helping the userto achieve an intended outcome with the required inputs and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, while displaying the home button (e.g., in the userinterface object or independent of the user interface object), thedevice detects (834) an eighth input by a sixth contact on the homebutton; and in response to detecting the eighth input by the sixthcontact: in accordance with a determination that the eighth input by thesixth contact meets home-button-activation criteria (e.g., lift-off ofthe sixth contact is detected with less than a threshold amount ofmovement to the left or right or before having been maintained for morethan a threshold amount of time, or before having met a second intensitythreshold, etc.), the device dismisses a currently displayed userinterface and displays the home screen; and in accordance with adetermination that the eighth input by the sixth contact does not meetthe home-button activation criteria and meets home-button-optionscriteria (e.g., the home-button-options criteria require that the sixthcontact is held for a first threshold amount of time or exceeds a secondintensity threshold, or includes a movement to the left or right, beforelift-off of the sixth contact is detected), the device displays a firstaffordance, which when activated (e.g., activated in response to a tapinput on the first affordance or activated in response to movement ofthe contact toward the first affordance followed by liftoff of thecontact), causes display of a user interface other than the home screen(e.g., the first affordance is for displaying a multi-tasking UI, thewidget screen, the voice-activated digital assistant screen, or the lockscreen). In some embodiments, when the home-button-options criteria aremet by the eighth input, the device concurrently displays the firstaffordance (e.g., to the left of the home button) and a secondaffordance (e.g., to the right of the home button), which whenactivated, displays another user interface other than the home screenand the screen that corresponds to the first affordance. In someembodiments, while displaying the home button, the first affordance, andthe second affordance, the device detects a ninth input that includesmovement of the sixth contact and lift-off of the sixth contact. Inresponse to detecting the ninth input by the sixth contact, inaccordance with a determination that the ninth input includes movementof the sixth contact toward the first affordance, the device transitionsto a second user interface (e.g., a digital assistant user interface)and in accordance with a determination that the ninth input includesmovement of the sixth contact toward the second affordance, the devicedisplays a third user interface (e.g., a multitasking user interface).Displaying the affordance for accessing a user interface other than thehome screen (e.g., a multi-tasking user interface, a widget screen, avoice-activated digital assistant screen, or a lock screen) in responseto a contact that meets home-button-options criteria enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the number of user inputs needed to accessalternate user interfaces and by helping the user to achieve an intendedoutcome with the required inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while displaying the home button (e.g., as part ofthe dock or separately from the dock) overlaid on a respective userinterface of a current application (e.g., at a later time after the userhas interacted with the device to display user interfaces of otherapplications) (836): in accordance with a determination that the currentapplication is an application of a first type (e.g., a maps application)(e.g., an application of which the user interface includes interactiveelements or variable content at the location that is occupied by thehome button when the dock or home button is not displayed), the devicedisplays the home button with a first transparency (e.g., home button issubstantially transparent over a maps application UI to reveal thecontent in the portion of the maps application UI that is below the homebutton); and in accordance with a determination that the currentapplication is an application of a second type (e.g., a voice-baseddigital assistant) (e.g., an application of which the user interfacedoes not include interactive elements or variable content at thelocation that is occupied by the home button when the dock or homebutton is not displayed), the device displays the home button with asecond transparency that is distinct from the first transparency (e.g.,the home button is substantially solid over the user interface of thedigital assistant). Displaying the home button with a first transparency(e.g., transparent) over a first type of application (e.g., anapplication with interactive elements, such as a maps application) anddisplaying the home button with a second transparency (e.g.,substantially solid) over a second type of application (e.g., anapplication without interactive elements, such as a voice-based digitalassistant) provides improved visual feedback to the user and allows thefull user interface of the interactive application to be visible to theuser. Providing improved feedback enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to achieve an intended outcome with the required inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

It should be understood that the particular order in which theoperations in FIGS. 8A-8D have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 600 and 700) are also applicable in an analogous manner tomethod 800 described above with respect to FIGS. 8A-8D. For example, thecontacts, gestures, user interface objects, tactile outputs, intensitythresholds, focus selectors, and/or animations described above withreference to method 800 optionally have one or more of thecharacteristics of the contacts, gestures, user interface objects,tactile outputs, intensity thresholds, focus selectors, and/oranimations described herein with reference to other methods describedherein (e.g., methods 600 and 700). For brevity, these details are notrepeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3 ) orapplication specific chips.

The operations described above with reference to FIGS. 8A-8D are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, display operation 802, detection operation 804, replaceoperation 806, detection operation 808, and display operation 810 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

1. (canceled)
 2. A method, comprising: at a computer system with a display and an input mechanism: displaying a first user interface on the display; while displaying the first user interface, detecting, via the input mechanism, a first user input; in response to detecting the first user input via the input mechanism: in accordance with a determination that the first user input includes a first type of interaction with the input mechanism, replacing display of the first user interface with display of a second user interface that is different from the first user interface; in accordance with a determination that the first user input includes a second type of interaction with the input mechanism, wherein the second type of interaction is different from the first type of interaction, initiating a process to power off the computer system.
 3. The method of claim 2, wherein the button is a power button.
 4. The method of claim 2, wherein the first type of interaction with the input mechanism includes a touch gesture on the input mechanism.
 5. The method of claim 2, wherein the first type of interaction with the input mechanism includes a slide input on the input mechanism.
 6. The method of claim 2, wherein the second type of interaction with the input mechanism includes a press input on the input mechanism.
 7. The method of claim 2, wherein the first user interface is an application user interface.
 8. The method of claim 2, wherein the second user interface is an application user interface corresponding to an application that previously displayed.
 9. The method of claim 2, wherein the first user interface corresponds to a locked state of the computer system.
 10. The method of claim 2, wherein replacing display of the first user interface with display of the second user interface includes switching the device from a locked state to an unlocked state.
 11. The method of claim 2, wherein: the first user interface corresponds to a locked state of the computer system; and the second user interface corresponds to an unlocked state of the computer system.
 12. The method of claim 2, wherein: the first user interface corresponds to a locked state of the computer system; and the second user interface corresponds to a home screen user interface, wherein the home screen user interface includes a plurality of application launch icons.
 13. The method of claim 2, wherein: the first user interface corresponds to a locked state of the computer system; and the second user interface corresponds to an application user interface.
 14. The method of claim 2, wherein: the first type of interaction with the input mechanism includes a touch gesture on the input mechanism; and the second type of interaction with the input mechanism includes a press input on the input mechanism.
 15. The method of claim 2, wherein: the first user interface is a first application user interface; and the second user interface is a second application user interface, different from the first application user interface, corresponding to an application that was previously displayed. 